What “senior engineer on every email” actually means.
We say it on the home page. Here is what it looks like inside an engagement — the response times, the code reviews, the decisions — in concrete terms a prospect can hold us to.
The home page says it: a senior engineer on every line, on every email, on every commit. This is the kind of sentence that wins a website award and loses a client. It has been used by enough firms in enough hero sections that it now reads as marketing posture by default. So here is what the sentence is supposed to do work — what the practice means when we put it on the page.
First reply lands in under twenty-four hours, in person, with a real answer. Not "we got your inquiry and will be in touch." Not a Calendly link with no human attached. A reply with the founder's name on it that actually engages with what you wrote. If your question was "can you build this for me by Q3," the reply says yes or no by Q3 with a specific reason; it does not say "let's hop on a call to discuss." The discovery call exists, but it is a follow-up to the written engagement, not a substitute for it.
Every line of code that ships under the engagement is reviewed by a senior engineer before it lands on your domain. Not by a junior who got a Slack thumbs-up from the senior; not by a CI bot that the senior trusts to flag the real issues. Code review at this practice means a senior engineer reads the diff, runs the change locally, thinks about the failure modes, and either approves it or rewrites it. The reason is structural — we built the engagement model on the premise that this is the minimum bar for "we shipped it," and we cannot move below the minimum bar without changing the model.
Architectural decisions are made by the same engineer that will own them in production. No "we'll figure it out at implementation time," no "the dev team will pick the framework," no decisions deferred to whoever happens to be on call when the code hits the editor. The framework, the database, the deploy target, the secrets-handling story, the dependency policy — all decided in writing before the build phase opens, by the engineer whose name will be on the on-call rotation when something breaks at 3 a.m.
The engagement portal carries the working relationship. Every estimate change, every revision, every reply, every file lands in the portal first — not in email, not in Slack, not in a "let's circle back next week" deferral. The portal is the source of truth and the audit log of the work (which we wrote about separately in [The portal is the product](/notes/the-portal-is-the-product)). The senior engineer on the engagement is the one updating it.
Email replies do not get delegated. Ever. If you sent the email to David, David replies. If David is on the other side of a deploy and cannot reply within twenty-four hours, you get a one-line acknowledgment from David that says "I will reply in detail by [specific time]" — and then he replies in detail by that time. Account managers, project coordinators, and customer success representatives do not exist at this practice. The senior engineer is the account manager.
The decision to walk away from an engagement is also a senior-engineer decision. This one matters and rarely gets said: if at any point during the work the senior engineer assigned to your engagement concludes the practice is not the right fit for the build — whether because the scope changed, the constraints became technically infeasible at the agreed price, or the relationship became something we cannot do good work inside of — that engineer says so, in writing, with a refund and a referral. The practice does not let a junior coordinator manage the offramp; the same engineer who would have shipped the work also signs the letter that says we will not be shipping it.
The compressed version of all this: the title on every contract, every reply, every commit, and every difficult conversation is the same one. There is no escalation path because there is no level above the engineer you are talking to. That is the structural meaning of the sentence on the home page.
If you read this and it sounds like a lot of work for one practice to commit to, that is precisely the constraint that keeps the engagement count where it is. We do not run more engagements at the same time than the bench can carry under this standard. The price reflects the bench; the bench reflects the standard. The home page sentence is the contract.