A corner shop and a state agency look like opposite customers. Here is why we hold both to the same engineering standard, and where the practice has to bend to fit each one.
On paper, the two clients have nothing in common. One is a family that owns a shop on a corner and wants a website that does not embarrass them. The other is a state agency that runs a service thousands of people depend on, governed by procurement rules, security reviews, and the patience of a long calendar. One decides over coffee. The other decides over months.
We build for both. People sometimes assume that means two practices wearing one name, a small friendly shop for the storefront and a stiffer, slower outfit for the agency. It does not. It is one practice, one standard, applied to both. The standard is the constant. What changes is the speed, the paperwork, and how the decision gets made.
This is the essay behind that. What a storefront and a statehouse actually share, where they genuinely differ, and why a small practice led by one accountable person fits both better than you would expect.
What they share
Strip away the size of the budget and the formality of the process, and the same four things matter to both buyers.
Prove it small before spending big. A shop owner should not wire thousands of dollars on the strength of a slide deck, and neither should a public agency commit a real budget to a vendor it has only seen pitch. So we do not ask either of them to. For a local business, that proof is a working prototype of the homepage, built and deployed before any money changes hands. For an agency, it is a pilot: a narrow, real slice of the work, scoped and delivered so the larger commitment rests on something you have actually seen run. Same principle, different size. Spend a little to learn before you spend a lot to commit.
Make the work inspectable. Evidence beats claims for everyone, but it matters more the higher the stakes climb. A storefront can click the prototype on a phone and judge it directly. An agency needs the same quality of evidence in a different form: a pilot that handles real cases, a build whose decisions are written down, code another engineer can read. In both cases the rule is the same. You should be able to look at the thing and check it, not take our word for it.
Build it so the next team can run it without us. This is the one buyers underrate until it bites them. Software that only its original author can operate is a quiet trap. For a small business it means being held hostage by a vendor who never wrote anything down. For a government, where staff rotate and contracts turn over, it is worse. So we build the boring way on purpose: clear structure, plain documentation, no clever tricks that only make sense if you were in the room. When we hand it over, the work is yours to run, change, or take elsewhere.
Stay reachable. A storefront wants to text a real person and get an answer. An agency wants to know who is accountable when something breaks at the wrong hour. Both are asking the same thing in different registers. Is there a human on the other end who owns this. The answer is yes, and it is the same human throughout.
Where they differ, and how the work adapts
Holding one standard does not mean pretending the two buyers are the same. They are not, and treating them as identical would serve neither. The practice bends in a few specific places.
Pace and risk tolerance. A storefront usually wants it this month. The owner can feel the gap between what they have and what they want, and waiting costs them business. We move fast and we keep the scope tight so fast is safe. An agency operates on a different clock by necessity. It answers to procurement, to security review, to accessibility and records obligations, and to a public that lives with the result for years. Moving carefully there is not bureaucracy for its own sake. It is the correct response to higher stakes and a longer horizon. We match the clock to the buyer rather than forcing one pace on both.
How the decision gets made. A shop owner decides. You look at the prototype, you talk it over, you say yes or no, and that is the whole process. An agency runs a process instead of making a call: requirements, evaluation, approvals, the people whose job is to ask hard questions before anyone signs. We are built to work either way. We can sit across a table from the person who owns the business, and we can also produce the documents, answer the questions, and meet the requirements a formal process demands. The method survives both because the proof comes first in either case.
Documentation and compliance depth. Every project we ship is documented well enough to hand off. Government work asks for more, and it should: accessibility standards, security expectations, records and procurement rules, audit trails that outlast any one person. We treat that depth as part of the job rather than a tax on it. The instinct is the same one a careful storefront build already has, written down so the next person can follow it, just carried further to meet a higher bar.
Accountability. When a storefront site has a problem, the owner wants it fixed and wants to know it will not happen again. When a public service has a problem, the same need carries real weight, because people are relying on it. We hold the higher version of that standard everywhere. It costs nothing extra to give a corner shop the same seriousness an agency requires, and it would be strange to do anything less.
Why a small practice fits both
The usual worry about a small practice is that it cannot be serious enough for government. The usual worry about a larger firm is that a corner shop will never be more than its smallest, least interesting account. A principal-led practice answers both.
There is no B-team handoff. At a larger shop, the senior person wins the work and a junior team you never met does the building. Here, the person who shows up is the person who builds and the person who is accountable when something goes wrong. End to end, it is the same hands.
The method scales in both directions without changing shape. Prove it small. Fix the scope so there are no surprises about price or delivery. Hand it over so you own it outright. That works for a single homepage and it works for a piece of a public service, because the principle underneath it does not care how big the budget is.
The three prototypes we have built so far are how we make this concrete rather than abstract. The Foot Store, The Griffon, and Ted's Butcherblock are real, clickable homepage prototypes we produced to show what we can do. To be plain about it, they are prototypes we built to prove capability, not sites we were hired to ship. They are proof for the storefront on its own terms, and they are proof for the agency too, evidence that we can take a real problem and turn it into a working, inspectable thing fast.
If you run a local business, you are the reason this practice exists, and you are first in line. The government work runs on the same standard you already get, which is the best argument we can offer that the standard is real. Either way, the deal is the same. We show you something that works before you commit, we build it so it is yours to keep, and the same person stays on the line.