Stop losing jobs you already quoted.
River~Code builds the quote follow-up, bid visibility and document systems that construction companies run their office on. Fixed price and a fixed date, agreed in writing before we start.
[ What we automate ]
- 01
Quote follow-up & bid visibility
The system that stops it happening again. - 02
Document intake & processing
Read, checked and filed without anyone retyping. - 03
Job reporting & compliance tracking
Assembled and sent without anyone remembering to.
… and plenty of other systems. These are the three we get asked for most.
You quote it. Then it goes quiet.
- A quote goes out. Someone means to chase it. Then a job starts, the phone rings, and it doesn’t happen.
- Nobody can say which bids are still open. They’re across three inboxes, a shared drive, and a spreadsheet someone updates when they remember.
- Subcontractor invoices, COIs and lien waivers arrive as PDFs and get retyped by hand.
- You don’t find out you lost it. You just never hear back.
A contractor quoting forty jobs a month who loses three a year to silence isn’t losing admin time. They’re losing six figures.
From nine manual steps to one system that runs itself.
Nothing changes about how your team works. It runs behind them.
- 01Inquiry arrives
- 02Sits in an inbox
- 03Somebody reads it
- 04Retyped into a spreadsheet
- 05Estimator emailed
- 06Costs dug out by hand
- 07Quote written up
- 08Quote emailed
- 09Nobody follows it up ✕
9 manual steps
- 01Inquiry captured
- 02Qualified & routed
- 03Estimator notified
- 04Quote sent
- 05Chased on day 3
- 06Won / lost logged
→1 workflow
Some of what we automate.
Quote Recovery System
Every quote followed up automatically, every open bid on one screen.
- Inquiry capture
- Qualification & routing
- Estimate request assembly
- Automated follow-up
- Open-quote dashboard
- Won / lost tracking
Document Intake Pipeline
Subcontractor invoices, POs, COIs, lien waivers and change orders read, checked and filed without retyping.
- PDF extraction
- Validation against the job
- Filing to the right folder
- Exception flagging
- Accounting handoff
Job & Site Reporting
The weekly report somebody assembles by hand, assembled for you.
- Progress pulled from your tools
- Scheduled assembly
- Sent to the client or the office
- Exception flagging
Compliance & Certificate Tracking
Insurance, licences and certificates chased before they expire, not after.
- Expiry tracking
- Automatic reminders to subs
- Document collection
- Status on one screen
These are examples, not a menu. If the thing eating your week isn’t here, describe it — the Roadmap exists to work out whether it’s worth automating.
How a build runs.
Three phases — and you have the price and the date in writing before the first one starts.
01
Map
Access, process mapping, specification signed off. You know exactly what’s being built, and what it costs, before anything is built.
02
Build
We build it, and you see it running on your own data — not a status report, not a demo environment. The thing itself, working, while there’s still time to change it.
03
Hand over
Testing on live data, training your team, a recorded walkthrough and a written runbook. Then we keep it running — handover is where we start, not where we finish.
One workflow is usually about three weeks. Bigger systems get split into stages, and every stage carries its own fixed price and its own date — so scope grows in steps you agreed to, not in an invoice you didn’t expect.
- What’s in scope
- What’s explicitly out of scope
- The definition of done
- Two rounds of revisions
- The price of a change request
All five, in writing, before you pay anything. This is our answer to “we tried this before and it didn’t stick.”
Three ways to work with us.
Real numbers, published. You don’t need a discovery call to find out what this costs.
Automation Roadmap
Find out where the money is leaking.
We map your process, count the manual steps, and give you a prioritised plan with costs.
What’s in a Roadmap →2 weeks
Automation Sprint
Fix one workflow, completely.
Built and live on your existing tools. Fixed price, fixed date, written definition of done.
How a Sprint runs →about 3 weeks
Automation System & Support
We build the wider system and keep it running.
Monitoring, maintenance, and one change a month.
What the retainer covers →+ $800/month
Start with the Roadmap.
Two weeks, $1,200, credited in full against a build. It tells you what’s worth automating, in what order, and what each piece costs.
Systems we’ve actually built.
A few examples of real projects we’ve delivered. What each one replaced:
Time tracking & payroll
- Before
- Everyone kept their hours in Excel. At month end somebody added them up by hand, per person and per project, then worked out leave separately.
- After
- Hours are logged as the work happens. Totals per person and per project, reports and leave balances all come out of the system — nobody re-enters anything.
Running today
Compliance assessment
- Before
- Each client’s environmental assessment was worked through by hand in a spreadsheet, by someone who knew the rules, one client at a time.
- After
- The client’s data goes in, the assessment runs itself, and the result comes back in a form the business can act on and take into a client conversation.
Running today
Mail & attachment routing
- Before
- Attachments arrived by email and were opened, renamed and filed into the right folder by hand, every time.
- After
- Mail is sorted and attachments filed on arrival, on the Microsoft tools the company already paid for.
Running today
Questions we get asked.
What if my team won’t use it?
They won’t have to. It runs in the background. If your team has to change how they work, we’ve built it wrong.
Do we have to replace our software?
No. We connect what you already have and fill the gaps between it. If a project requires you to migrate systems, we’ve scoped it wrong.
Who maintains it?
We do, monthly. That’s the actual product, and it’s why the retainer exists.
Does this work with our PM tool?
Usually, yes — Procore, Buildertrend, and most of the others expose enough to connect to. Where a tool doesn’t, we build around it rather than ask you to replace it.
Our estimators aren’t going to use a new system.
They won’t have to. The follow-up runs whether or not anyone opens a dashboard. The dashboard is for whoever wants to know what’s open.
What if you disappear?
You own everything we build: code, workflows, accounts, credentials. Everything is documented in a runbook at handover. Another developer could pick it up.
Where does my data go, and can you sign an NDA?
We use AI tools as part of how we build, so some project content passes through third-party AI providers as part of the development process — we won’t pretend otherwise, and it means we can’t offer the kind of absolute confidentiality a formal NDA implies.
What we do commit to, in writing: we never disclose that we work with you, discuss your business, or share your documents or data with anyone outside the project. If your work requires a stricter data-handling standard than that, tell us before we start and we’ll tell you honestly whether we’re the right fit.
Do I own what you build?
Yes. Entirely, from day one, in writing.
Find out where the money is leaking.
The Automation Roadmap maps your process, counts the manual steps and prices the fix. Two weeks, $1,200.
We reply within one business day.