built to order
Custom software development for US companies, live in 30 days
Your team works US hours, signs US paper and answers to a US board. We build to that: an MSA, a fixed-price SOW per phase, standups inside your morning and a working system in 30 days from engineers with 25+ years in production.
Send the spreadsheet today. Within 48 hours an engineer sends back a fixed price and a start date.
USA
Excel, an Access file, email threads and a reconciliation someone redoes by hand every morning.
- spreadsheet + emailExcel · Outlook
- access.mdbAccess
- manual reconciliationpeople
- shadow ITunowned
30 days from spreadsheet to production
A Go service, a TypeScript web client, PostgreSQL with migrations and an append-only audit log.
- domain serviceGo
- web clientTypeScript
- postgresschema + migrations
- audit logappend-only
What we put in writing for US clients
- An MSA with a SOW per phase
- One master agreement, then a short statement of work for each phase with its own deliverable, date and fixed price. Delaware, New York or California law, or whichever your counsel prefers.
- IP assignment on payment
- Work product transfers as each phase is paid. If you are acquired mid-project, or your board wants the asset on the books this quarter, you already own every line you paid for.
- Overlap written as a number
- 4 hours with US Eastern and 3 with Pacific, in the SOW as a commitment. Standups land inside your morning, and anything urgent outside that window goes to a named engineer.
- Vendor onboarding without drag
- W-9 on file, certificates of insurance, your security questionnaire and your vendor portal. We go through US procurement like any domestic vendor and answer every form in writing.
- Your data stays in the US
- The work runs in your cloud account in a US region or on machines in your building. Our fine-tuned models run there air-gapped, on your hardware or on hardware we supply.
From spreadsheet to production in 30 days
- 01days 1–3
Watch the work happen
We sit with the people who run the process and read every formula in the spreadsheet. The exceptions they handle without thinking go into the spec on day one, while they are still cheap.
- 02days 3–7
Model the data and the rules
Schema, states, who may change what. Every argument about the rules happens now, at a fraction of what it costs the night before launch.
- 03days 7–20
Ship one path end to end
Input to report, in production, used by the people who do the job. They find the gaps in real work and our engineers close them the same day.
- 04days 20–30
Migrate and switch off the file
We import the history, reconcile every row, run old and new side by side, then remove write access to the spreadsheet. From day 30 the work happens in one place.
What the platform does, what our engineers do
Reading your Access queries and Excel formulas
Platform
Every formula comes out as a plain rule your team can confirm at a glance.
Deciding which rules are real and which are habit
Engineer
Only your people know the Tuesday exception exists because of one supplier. Our engineers ask until they find it.
Service, schema and migrations
Platform
Generated from the agreed model and reviewed line by line before it merges.
The screens people use all day
Both
An engineer designs the daily path. The admin forms around it come off the platform.
Importing and reconciling the history
Both
The platform loads every row. An engineer decides what happens to the rows that never balanced.
Cutover
Engineer
The date, who is on call and the rollback, written down before anything switches.
Every generated file lands as a pull request, reviewed by the engineer who will answer for it in production.
The engineers who build it
Our engineers have been shipping production software for more than 25 years, and they are the best people you can put on this work. They have moved scheduling, claims, billing, inventory, dispatch and reporting off Access, Excel, VB6, Delphi and PHP dozens of times. The shape repeats, so they know where your process will bend before you show them.
Fixed price per phase, the delivery date in the contract, and the code in your repositories from the first commit. A phase that misses its spec is not accepted.
What buyers ask before they sign
Will you sign our MSA?
In most cases, yes. We read IP assignment timing, the liability cap against contract value and the non-solicit first. Anything that would block a fixed-price phase comes back as a redline with the reason written beside it. Attach your paper to the form and the redline travels with the quote.
Do you invoice in dollars?
Yes. Payment terms follow your AP department, and net 30 is the usual. If procurement needs a domestic counterparty on the contract, say so in the form. The paperwork adjusts, and the price and the date stay where they were.
Who is on the project, and where do they work?
Senior engineers with 25+ years in production. The person answering your questions is the one reading your code, with no account manager in between. Remote is the default, inside your VPN is common, and on-site days go into the SOW when your rules call for them.
Can the work stay inside our perimeter?
Yes. For regulated records our fine-tuned models run air-gapped in your US cloud region or your data center, on your hardware or ours. Nothing about your code leaves the building. Mark it in the form and the quote is priced for it.
What do we hold when the project ends?
Repositories in your organization from the first commit, tests written against the behavior of the old system, a current map of the codebase and a runbook. Nothing calls back to us at runtime and there is nothing left to rent. Get a quote and the handover list comes with it.
Show us the spreadsheet
Attach the file or describe the process and who touches it. You get a fixed price and a start date within 48 hours. Thirty days later the spreadsheet is read-only and the system runs the work.
The first reply comes from an engineer with 25+ years in production, usually asking who owns the process today.