Operational platforms that fit mid-sized companies.
For companies the big vendors won't build for.
Fixed price. One owner. AI-ready.
Mid-sized operators outgrow their spreadsheets and homegrown systems long before enterprise software will right-size for them. We build the integrations, screens and automations that take the manual work out of billing, reconciliation and reporting, and leave the business ready to adopt AI on its own terms. Unlike enterprise vendors or staffing shops, one engineer owns delivery end to end on a fixed price, with fifteen years across rail, healthcare, insurance, retail and education.
Is this you?
7 situations
You have real domain experts and fewer than two developers, and the vendor that owns your industry quoted you like you were ten times your size, or wouldn't quote you at all.
You own the business.We own the platform.
You have the domain experts, the customers, and the process. What you don't have is an engineering team, and hiring one to build one system is the wrong trade. We take the platform: architecture, delivery, hosting, and the SDLC, run through your people rather than around them.
Your data is yours. Anything you brought with you is yours, in writing. What we own is the platform we build and run, and owning it is what lets us carry the reliability, the testing and the upkeep instead of handing them back to you.
A perpetual license to what we built, for as long as you want it.
First Build$5,000
Done inside 30 days. Usually two weeks.
We find the thing costing you the most, and we build the fix.
What you get
Working software, hosted and run by us. The screen the work actually needs, a report that finally answers the question, two systems made to agree, a daily job that runs itself, or something finally off paper. You get a perpetual license to use it, for as long as you like, whether or not we are still in the picture.
What we need from you: two to four hours.
- 1Access to the systems in scope: credentials or a screen-share
- 2Two to four hours of the person who actually knows the process
- 3One named decision-maker who can approve the fix
$5,000 fixed price. Delivered inside 30 days.
Our guarantee
If we're late because of our capacity or a gap in our plan, we keep building at no charge until it's done. The clock pauses only while we're waiting on one of the three things we need from you.
This is deliberately small. One fix, not a platform, and that is the point. You find out what we are like to work with on one contained thing, for a number you can approve yourself, before anyone talks about a bigger system. If it goes badly you have lost $5,000 and two weeks. If it goes well, you know something about us that no case study would have told you.
What the $5,000 covers
We find it.
Discovery and planning on our time, ending in the one thing costing you the most.
We build it.
One integration, automation, screen or report. Working software, not a document.
We run it.
Hosted, monitored and maintained by us, for as long as you want us to. You do not need an ops person.
We document it.
Documentation and tests written as we go, not assembled at the end.
We hand it over.
A perpetual license, a copy of the repository, and thirty days' notice either way. Handover is a deliverable, not a negotiation.
We guarantee it.
Late through our fault and we keep building at no charge. And for sixty days after it goes live, anything you want corrected about what we delivered, we correct. That is included.
What the thirty days looks like
Before any build
We start with a user story.
Before anything gets built, we write down what you should be able to do when this is finished, in plain language, and what it will cost to run once it is live. You approve both. If we have picked the wrong thing, this is where saying so costs nothing.
About a week in
Review one.
You see the design of what you are getting and confirm it does what you need. This is a design review, not a demo of finished work.
About week two
Review two.
The same thing, now wired into your real systems and working.
Then
It goes live.
For sixty days
You run it, and we stay on it.
Run it for real, in production. For sixty days after it goes live, anything you want corrected about what we delivered, we correct. That is included, not a change order.
Most builds are done in two weeks. Thirty days is the outside.
What happens after
A First Build fixes one thing. What it also does is tell you which of these you actually need next, with evidence rather than a guess.
Build what's missing.
The screens, forms and worklists your system was never going to give you, built on top of what you already run. This is the most common one, and nothing gets replaced.
Connect what you have.
Your systems are fine on their own. They just don't talk to each other. We build the integrations and automations between them, and nothing gets replaced.
Replace one system.
One of them is past saving. We rebuild that one to fit how you actually work, and leave everything else alone.
Consolidate.
Several systems become one platform, phase by phase, each phase ending in working software you accept before the next one starts.
Daniel P. Chan
Founder & Engineer
Fifteen years of business systems. Seven of them running car repair billing and AAR data exchange for the rail industry, eight building operational platforms across other industries.
Areas we work in
- Rail
- Healthcare
- Insurance
- Materials & Logistics
The questions you're already asking
One developer is not the job. Building and running a platform is a senior engineer, the developers under them, someone to keep it running in production, someone to own the scope, and someone to manage all of it. At market wages that is over a million dollars a year, before benefits. That is why companies your size do not have an engineering team, and it is the reason we exist.
You are the size the big vendors won't serve. A First Build exists for one system and one pain.
Vendors sell their product. We build to your operation, around the way your people already work.
We keep the code and you get a perpetual license to run it, for as long as you want it. That is what holds the price where it is. If you want to own it outright we can price that, and it is a decision you can make later rather than now.
Your documentation, your tests and a current copy of the repository are handed to you as a deliverable, not negotiated at the end. Your license to run what we built does not expire and does not depend on us. Thirty days' notice either way. If you leave, you take your data in a usable format, and you can buy the system outright and move it.
Working software inside 30 days, usually two weeks. You approve a written scope before anything is built, you see the design about a week in, and you see it working against your real systems about a week after that. Then you run it for real, and for sixty days after launch we correct anything you want corrected. Anything beyond that is sold phase by phase, and each phase ends in software you accept before the next one starts.
Neither are we, not at $5,000. A First Build adds one thing to what you already have and replaces nothing. If a system does eventually need replacing, that is a later decision made with evidence, after you have seen us work.
Sometimes we have. Rail, healthcare and insurance are three of the five behind those fifteen years. Where we haven't, your people know your industry better than any vendor will, and what they don't have is an engineer. We own the platform work and run it through your experts, which is exactly why we ask for two to four hours of the person who actually knows the process.
We price that with you before you approve the build, based on what it actually uses. It is a monthly or yearly subscription, and you can end it on thirty days' notice.
We use AI tooling in delivery. We don't price a schedule on it, and we'll tell you exactly where your data does and doesn't go.
Start with the thing costing you the most.
One step closer to a right-sized operational platform for your business.
$5,000 fixed price. Delivered inside 30 days.