Joshua Hill · Bellingham, WA · 20 years writing winning energy bids
A document desk for ROW and land-services firms: scopes of work, estimates, and change orders on your client's template, priced from the current rate sheet, audited line by line against the source. No new software, no portal, no coordinator to hire. AI systems I built and host on my own servers do the assembly; I still write and sign every page that ships.
12+ months in live utility production · 16–20 documents a week · every page audited and signed
Have an RFP instead? Send it for a free bid/no-bid read, in writing, inside 24 hours.
The salary bar above is before benefits, software, and ramp-up time. And at one to three documents a week, a full-time hire spends most of the year waiting for intake; you pay for the desk whether or not the email arrives.
When field agents write their own scopes, you're paying field rates for paperwork and losing the field hours too. The documents also come back formatted six different ways depending on who wrote them.
A scope priced on the wrong rate sheet comes back for rework, and repeated format rejections put the MSA itself at risk. Every document I ship is audited against the source, with the checklist attached to prove it.
Live production figures, current as of August 2026
12+ months
Scopes, estimates, and change orders delivered weekly to one utility contractor, through engineer turnover and rate-sheet changes.
16–20/week
Current document volume, sustained week over week.
Same day
Turnaround target from the engineer's email to a submission-ready document.
0 ever
Documents shipped without the line-by-line source audit and my sign-off.
A small land-services firm holds a standing contract with a major investor-owned electric utility. Every project arrives the way yours do: an engineer's email, parcel details, a rate-sheet reference, and a deadline. What has to come back is a priced individual scope of work on the utility's own template, correct to the source, ready to submit.
I built the pipeline that does it, and it has run for over a year, growing from a few documents a week at the start to sixteen to twenty a week now, surviving a full template revision and multiple rate-sheet changes along the way.
The client and the production history are real. The identifying details are reconstructed because the actual documents are confidential, and yours would be handled the same way.
The part most firms ask about first
The models that assemble your documents are private LLMs I host on my own servers. Nothing goes to a public AI service, nothing trains anyone else's model, and no client can see another client's work.
Under NDA, I train your model on your firm's own document history: the templates, the rate structures, the phrasing your client already approves. Every document after that comes out sharper, because the training set is work that has cleared review.
Six years ago I started engineering my practice with conventional automation. Two years ago, private LLMs made end-to-end assembly possible. Through all of it, I've read every document against the source, and nothing ships without my sign-off.
Put these numbers in your job costing before you send the first email
Most firms start here
$250 /document
$150 /document
$950 /month
No hourly meter, no percentage of contract value, no other fees. The only other number: one-time onboarding on your firm's own document history is $750, and it is waived on pilot projects started before October 1.
I cap intake so my sign-off never gets skipped, and if the calendar's full I'll tell you before you send anything.
1
I sign before I see anything. Then send a live project: the engineer's email, parcel details, your client's template, the current rate sheet.
2
Priced and formatted, with a verification checklist showing each task traced back to the source email. I've signed off on the audit before you ever see it.
3
Against your own standard, on your own work. If it's not submission-ready, tell me. The first one's free either way.
4
The flat rates above apply, with the retainer offered at 60 days. Governance, security, and the continuity plan are written out on the process page.
I'm Joshua Hill, a proposal and grant writer with a computer engineering background, formally certified in the bid-development methods the largest government contractors use to win. Six years ago I started building automation around my own document work; two years ago, privately hosted LLMs made a true end-to-end pipeline possible.
What you get is the writing I've always done, with better instruments behind it, tighter compliance, and a real cost advantage. I still write, and I sign everything.
Client names stay off the page because my agreements keep them there, and yours would too. On a call, with references, I can be specific.
The pipeline does the assembly: it reads the intake, pulls the rate sheet, fills the template, and checks the math. I wrote these documents by hand for twenty years, and I still read every one against the source before it ships. Nothing goes out without my sign-off, and you judge the result on your first document, which is free.
To my servers and nowhere else. The models are sandboxed, privately hosted LLMs under my control, so your documents never touch a public AI service and don't train anyone else's model. No other client can see them, and the NDA comes first.
No. The pipeline runs entirely on email and your client's own Word template. It can also read KMZ files, plan sets, and photos when your projects include them. Your engineers keep emailing the way they already do; you forward it.
Holding that is most of the job. The pipeline carries each client's template and current rate structure, and it survived a full template revision and multiple rate-sheet changes at the firm it was built inside. If you're carrying several utility clients at once, that's the situation this was built for.
More than you'd expect, because your first project already carries what matters most: the engineer's email holds the scope, your client's template holds the format, and the rate sheet holds the pricing. What an untrained pipeline lacks is your firm's phrasing and edge-case habits, so on early documents anything ambiguous comes back to you as a question instead of a guess, and I carry the gap by hand until onboarding closes it.
For a full RFP, the compliance matrix and outline come from the solicitation itself the same day; your win story comes from a short call and a five-item document list.
Yes, and I expect to. Everything runs under confidentiality as standard; that's why the case study on this site is anonymized.
You keep operating. Your templates, rate sheets, and every document produced live in your own systems, and there's nothing installed to break. The full continuity plan is on the process page.
There's a scoping email you've been putting off. Forward it and the finished, priced document comes back free. No onboarding first: document one is built from that email, your client's template, and the current rate sheet.
josh@outcomesautomation.com · Replies come from me, usually within one business day.