built to order
Custom software development in New York, live before your close
Your firm has a VBA model three desks depend on, an AS/400 running policy administration and a batch that must finish before the open. Our engineers have 25+ years in production and move all of it to Go and PostgreSQL in 30 days.
Send the spreadsheet today. Within 48 hours an engineer sends back a fixed price and a start date.
NYC
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 New York work demands
- Your calendar sets the cutover
- Settlement cycles, the month-end close, filing dates. Phases end where your calendar allows a change, and a batch that must finish before the open switches on a date you pick.
- Parallel runs to the cent
- Old and new process the same inputs and are compared to the cent before anything takes over. For month-end jobs we replay the month you already recorded, so a quarterly close never adds a quarter to the project.
- An audit trail built for examiners
- Append-only logs of who changed what and when, plus the comparison report kept as evidence. FINRA, SEC and NYDFS examiners ask for the reasoning behind a number, and you hand it over.
- The AS/400 nobody wants to touch
- RPG policy administration, green screens your operators fly through, DDS files carrying twenty years of history. We move job streams one at a time and keep the keyboard-first flow your operators know.
- The model on one person's laptop
- A spreadsheet with VBA that three desks depend on and nobody has tested. It becomes a service with a schema, an owner and a test suite built from the results it already produced.
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
Our deadline is a settlement date. Can you plan around it?
Yes, and every New York plan starts there. Phases end where your calendar allows a change, the comparison run finishes before the window opens, and no job switches until it matches the old output on your own recorded data. Put the dates in the form and the plan is built on them.
Will an examiner accept a rewritten system?
Examiners ask for evidence, and the parity harness produces it: the same inputs through both systems, every difference at zero or signed off in writing. The report is yours, and it answers the question a year later when nobody remembers the project. Name your regulator in the form.
Our operators are faster on the green screens. What happens to them?
They keep their speed. The replacement is keyboard-first and follows the flow they already know, and the 5250 screens stay up until the new path is provably identical. Operators sit in on the design sessions from day one. Send us the screens they live in.
Can you work inside our network?
Inside your VPN is the default here. For regulated work our fine-tuned models run air-gapped in your data center, on your hardware or on hardware we rent you, and nothing about your code leaves the building. List your constraints in the form and the quote is priced for them.
How fast can you start?
Within 48 hours of a signed statement of work, with discovery running while legal finishes. Thirty days is the ceiling on the whole project, and the phase plan shows which piece lands before your next close. Send the system today and the plan is back in 2 days.
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.