Discovery and working prototype for Firstwater Custom Builders
A $700,000 draw runs about 700 pages of backup, collected, printed, scanned and ordered by hand. In under a month you will watch a real one assemble itself.
Four things decide what the full system costs and how long it takes. Every one is unresolved today, and every one is answered in this phase with evidence rather than an estimate.
Everything downstream depends on how your QuickBooks can be read. A desktop company file and a browser login are two different pieces of engineering, and the difference is the single biggest variable in the price of the full build. We confirm which one you have, connect to it read only, and prove it moves real data before anything else is built.
We measured your bookkeeper against 650 of her own coded bills. Across 124 vendors, 117 have only ever used one code, and her coding is predictable from the vendor alone 95.5 percent of the time. That is most of the coding problem solved before we start. What is not yet proven is which job a cost belongs to, because the export we have carries no job column. We get the corrected export and measure allocation the same way.
Your billing rules are not in QuickBooks and they are not in the spreadsheet. They are in the signed contracts, and the four jobs in scope use three different models. Kares is a fixed fee with a seventeen draw calendar and supervision folded into the fee. Connell and Lewis are twenty percent on cost with supervision billed separately, at different rates. Meran is fixed price. We encode all four, and every rule we extract cites the page it came from so you can check it.
The five summary pages plus a backup packet ordered to match the invoice lines, bookmarked and numbered. It has to reconcile to Kares Invoice 1 to the penny, and we already know that answer is $79,715.44, so this either passes or it does not. It also has to satisfy the contract rather than merely look like your current output, which means the cleared checks your agreement requires alongside the paid invoices.
What it is: software that assembles one real Kares draw end to end, that you can use and watch run.
What it is: the same five pages and ordered backup you send today, checked against $79,715.44 on Kares Invoice 1.
What it is: fee, draw schedule, labor rates, retainage and deposit terms for each job, every line citing its source page.
What it is: read only, evidenced, with the integration path for the full build settled rather than assumed.
What it is: one number instead of a range, built on what we found rather than what we guessed.
50% to begin
You see real work every week, and the last week ends with a packet you can hold.
QuickBooks edition confirmed and connected. Corrected cost export in hand. Signed Meran agreement collected.
Invoices pulled straight from the bookkeeper inbox. Coding and job allocation measured against your own history.
All four contracts encoded as billing rules, each line citing its source page, reviewed with you.
The Kares packet assembled, reconciled to the penny, and load tested at full size.
Findings, a walkthrough with Morgan, Brian and Haley, and a fixed price for the build.
First step: accept below and we start inside two business days.
Your time cost: one hour with Haley in week one, and a review session in week three. Nothing changes about how anyone works in the meantime.
Success looks like: a Kares packet built by software that reconciles to $79,715.44 and satisfies the contract.