Field notes · July 16, 2026 · Valentor
Every engagement we sell starts with a one-page scope: the deliverable, the acceptance criteria, the deadline, the price. All four in writing, before either party signs. If we cannot write that page, we do not take the work. A two-person senior firm has no honest way to sell anything else, and we think a written scope is also the best way for a small or mid-market buyer to purchase development or marketing work, whoever they end up hiring.
What hourly billing actually sells
An open-ended retainer sells you access to effort, not an outcome. The vendor invoices for time, so the risk of ambiguity is yours. If the brief was vague, the discovery of what you actually needed happens during the build, on your invoice. Nothing in that arrangement pushes the vendor to finish. Slow is billable. So is rework, and so is the meeting about the rework.
Most agencies are not cynical about this. The problem is structural: a firm that cannot predict its own delivery cost has to bill hourly to protect itself, which means the client absorbs the uncertainty instead. A large enterprise can carry that risk across a portfolio of vendors. A forty-person Virginia company buying its first custom application cannot. One bad open-ended engagement is the software budget for the year.
Scope in writing, before the signature
Our fix is procedural. Before a contract exists, we produce a scope document: what we will build or audit, what "done" means in testable terms, what is excluded, when it lands, and what it costs. The price is fixed. The document is specific enough that you could take it to a competitor and get a comparable bid. We consider that a feature.
We sell four shapes of engagement. Audits: code, infrastructure, or marketing analytics, with a written findings report at the end. Sprints: a defined feature or campaign asset list, delivered in weeks. MVP builds: a scoped v1 with an explicit cut line for everything that is not in it. Retainers, but only with defined service levels: named response times, a monthly deliverable list, a renewal decision every quarter. A retainer with an SLA is a scope that repeats. A retainer without one is a subscription to good intentions, and we do not sell it.
One habit from military planning survives in this process, and only one: commander's intent, the end state written down before anyone moves, so every later decision can be tested against it. Our scope document does that job. Everything else about how we work is ordinary engineering discipline.
Why two seniors can price the risk
Fixed pricing is only rational when you can estimate, and estimation fails at handoffs. In the pyramid model, the person who scopes the work never touches it: a partner sells it, a project manager translates it, juniors build it, and every layer between the promise and the keyboard adds variance. A pyramid firm cannot quote a fixed price honestly because it does not know what its own delivery will cost.
We removed the layers. The founder who writes your scope document is the person who does the work. No account manager, no handoff to a bench of juniors. When the person estimating is the person delivering, the estimate is a commitment, not a forecast.
AI tooling is what makes this economical in 2026. Code generation, test scaffolding, and research agents now do most of what agencies once staffed junior layers to do. Two senior builders working with that tooling can produce what used to require a team of six, without the coordination overhead the team of six exists to manage. The pyramid was an economic artifact. The economics changed, and we built the firm the new economics allow.
The cost of this model, paid by both sides
Fixed scope means we say no more often than most vendors you will talk to. That is the honest part of the pitch, so here it is in full.
We say no to vague briefs. "Modernize our web presence" is a wish, not a scope. When a brief arrives in that shape, we will not quote it. We will either propose a paid audit whose deliverable is the scope document itself, or we will tell you we are not the right firm for the job.
We re-scope changes instead of absorbing them. Mid-project, when you want something outside the written scope, you get a written change order: what it adds, what it costs, what it moves. We will not quietly absorb it, because absorbed changes are never free. They come out of quality or schedule at a place where you cannot see the withdrawal. A change order makes the cost visible and puts the decision back in your hands.
The risk on the estimate itself runs the other way. If we misjudge how long the work takes, that loss is ours. The price does not move because our estimate was wrong. That is the other half of the deal, and the reason we scope carefully before signing.
How to start
We are a new firm and we do not pretend otherwise: Valentor Services Group LLC, formed in Virginia in July 2026, SBA SDVOSB certification in progress. We run our own paperwork by the rule we sell. The SBA veteran-certification application we are working through is a fixed checklist of documents, and the agency reported average processing of 12 days as of November 2025 (SBA, Nov. 11, 2025). Defined inputs move fast. Vague ones wait. That pattern holds everywhere we have looked, and it is the pattern we sell.
If you have a project, send the brief in whatever shape it exists. One paragraph on the problem and one on what done would look like is enough. Email contact@valentorgrp.com. You will get one of three replies: a one-page scope with a fixed price, the specific questions we need answered before we can write one, or a straight no with the reason. No discovery-call funnel, no proposal theater. The scope comes first, or there is no deal.