Where AI is worth doing around Washington
For a twenty-person consultancy in Arlington, the next customer is not hard to name. It is another agency, a state government far outside the Beltway, or a commercial buyer who needs the same skill. The shortage that keeps the firm from bidding is hours. Every bid is a proposal, and the people able to write one are the people already billing on the current contract, so the firm passes on work it could do well. Its office and its twenty people can stay exactly where they are. The proposal is the thing that travels to the new customer, and the firm needs to be able to write more of them.
What fills the week in that office is assembly. A solicitation arrives with its requirements, and someone copies them into a checklist. The past-performance section is rebuilt from earlier proposals each time. At the end of the month the timesheets are retyped into a report in the form each customer wants, and the statements of work are checked against the invoices by hand. Little of this is judgment; it is putting what the firm already knows into a required shape. An association office here has its own version, in member questions, renewals and board reports that come round again every month.
We turn that assembly into software, one document at a time. The monthly report is the likely first one; its hours are counted before and after the change, and a second document waits until that count is in. We run our own businesses this way, with court-record lookups and reminder texts handled by software we built, and nobody lost a job. For the consultancy, the software lays out each customer's report from the timesheets, and a manager corrects and signs it. The solicitation checklist and a first draft of the past-performance section come later, drawn only from the firm's own earlier work. Its people still decide what to claim, what price to offer and whether to bid at all, and anything the software is unsure of is marked for them instead of guessed.



