Questions people ask.
If your question isn't here, ask it on a call.
Can I edit the site myself, or do I have to call you for every change?
On a WordPress build, you can change routine content yourself: hours, prices, and photos for a storefront; events, statements, leadership, and campaign pages for an organization. On a custom-coded site, routine edits usually come through the ongoing plan instead. We tell you which model we're proposing, and who will make each kind of change, before work starts.
What's included?
It depends on the project. It can be a public site, a booking flow, a members-only portal, a custom app with a backend, employer or market research, or some combination. We do not sell fixed packages. We scope the work to what you need and tell you what is in and what is out before you commit.
What's included in the monthly?
Hosting and security updates, accessibility upkeep, performance and uptime monitoring, and a person who answers when you email. Routine content changes are handled for custom-coded sites; WordPress clients can make them directly and can still send us the ones they'd rather not handle. The agreement spells out ownership and includes a documented handoff if we part ways.
What's a typical timeline?
A focused site usually takes a few weeks from kickoff for a local business, depending on how much content you have ready. Apps with a custom backend take longer, and research runs on its own clock. We give you a specific timeline up front, and if something has to be live before a launch or a press call, tell us and we'll plan around it.
What technology do you build on?
We use WordPress when your team needs a familiar editor and a custom-coded build when the design, interaction, or data work calls for it. Either way, the site has to load fast, stay portable, and meet accessibility standards. We explain the recommendation before you commit.
Can't we just add an accessibility overlay?
No, and we'd steer you away from paying for one. A script added to a finished page can't cover what an audit or a Section 508 review looks at, and automated fixes reach only part of the standard. The people overlays are meant to help often switch them off. We fix the site itself and test it by keyboard and screen reader. How we build accessible sites.
What happens if we part ways?
Our standard agreement is structured so you keep the site, domain, content, and commissioned research, subject to any third-party licenses named up front. We document the handoff so another developer can pick it up.
You've never worked with someone exactly like us.
Maybe not, and we will say so. Lincoln builds web applications for a public research program at UCLA, and we built and still run the organizing platform for our own union. We will tell you which parts of your project are new to us.