We build one system that runs your whole operation, hand you the source, and price it before we begin. For companies of 5 to 50 people. Based in Los Angeles, working everywhere.
A twenty-person company now runs on eight or ten subscriptions that don’t agree with each other. The CRM says one number, the books say another, and somebody spends Friday finding out which is right. Each product bends your process to fit its features, charges by the seat, and returns your own data through an export screen.
Stop bending your business around software built for somebody else.
We build the fitted system at a size and price for companies of 5 to 50 people: one platform for the whole operation, shaped to how you already work, live in weeks. And when we leave, nothing about it depends on us:
We scope by counting the workflows your business runs on — a job from booked to paid, a work order from scheduled to closed, an invoice from drafted to cleared. Each is a pipeline: one record type moving through its lifecycle. The count sets the price, and the specification shows the arithmetic behind it — the hours your team spends copying data between systems and chasing down mismatched numbers, priced at their wages, plus the subscriptions the system retires. If that math doesn’t repay the fee several times over in the first year, we say so on the call. Below is who we serve and what each engagement costs.
An accounting app, a starter CRM, a scheduling tool, and a spreadsheet per department. Productized software runs each task well enough; nothing runs the business. One person knows how it all fits together.
Tear it down. At this size there is rarely anything worth keeping but the data, so the whole operation moves into one system, built in four to six weeks.
A free scoping call is the choice point: you either pick the package or the retainer. The package runs four to six weeks from first interview to a running system — design, build, deployment, training, and thirty days on call after.
The small business service package: everything moves into one system you keep. Best for businesses modernizing the whole operation at once, rather than improving an existing one.
$10,000 fixed, in three payments — $1,000 at specification, $3,000 at prototype, $6,000 at deployment.
A CRM, an industry platform at the core, payroll, books. Each fine on its own, none agreeing with the others, and the reports rebuilt by hand every week.
It depends on the stack. We keep and connect the systems worth keeping, and replace the rest. Many clients start with one painful problem — usually reporting — so you can judge the work before committing to more.
A free scoping call and a pipeline count first. The call is the choice point: the package, or the retainer if there’s a lot you’ll be keeping.
You might fit the small business package as it stands — one system, built at once, the source in your hands. The specification says exactly how far the package stretches.
The package starts at $10,000; more extensive migration or additional pipelines can carry the price as high as $30,000, quoted in writing before we begin. Or the retainer: a $3,000 monthly minimum, drawn down against hourly work, with the rate quoted on the scoping call.
An ERP or industry platform at the center, satellite tools around it, integrations nobody fully trusts, and a backlog your vendor will never build. All of it productized; none of it yours.
Usually, keep the core. We engineer within the stack you have — untangling configuration, connecting silos, automating between them — and replace pieces only when the numbers say to.
Scope first, quote second, a written specification you approve before any money moves. Work deploys in increments, so the first pipeline is earning while the last is still being built.
Usually the retainer — for when there’s a lot you’ll be keeping: your existing core kept and untangled, improved piece by piece. What we build under it you keep on the same terms, and if you ever stop, nothing switches off.
Outside of the package, we work on retainer: a $3,000 monthly minimum, drawn down against hourly work. The rate is quoted on the scoping call, before anything is billed.
None of this is a rule. A fifteen-person company can have an enterprise-grade mess, and a forty-person company can fit the package. The scoping call is where we count what you actually have, at no charge.
Discovery, design, build, deployment, and training: in four to six weeks, everything moves into one system you keep. You are the COO, and we are your hands in the weeds.
Every core pipeline moves from spreadsheets and legacy tools into one system, counted and quoted on the scoping call. Ten or fewer pipelines with minimal migration qualifies; if there’s a lot you’ll be keeping, the call points you to the retainer.
Dogma, our own platform, is the answer. It maps processes and models unique businesses quickly, so our hours go into your system instead of the scaffolding under it: rapid, iterative deployment and revision, on a foundation built for exactly that.
An extensible framework built for flexibility and ease of configuration in the hands of experienced consultants. Every engagement is built on it and configured to the business as it actually runs.
Rapid drafting, deployment, and revision of business processes. It lets us meet you where you are while exposing the best opportunities for automation.
Tools for correcting processes while they run. When live work hits a case the map never covered, the process’s guardrails come down on the spot, the fix is drafted without leaving the ERP, and the new path publishes against running work. Problem and solution stay in one system, so every exception leaves the map more complete than it found it.
A build in progress. We draft each of your processes, wire in its automations, and connect one to the next until the business runs as a single system. In our hands that takes hours, which is how a team of four delivers a full transformation in weeks.
01Draft: steps drop onto the canvas, and the process takes shape between them.
02Wire: each step declares what it requires and what it automates.
03Connect: one process hands off to the next: a finished job creates its own invoice.
04Publish: the impact check clears, and the process goes live mid-operation.
The same tool after launch. When a live process meets a case the map never covered, we branch it, wire the new path, and publish against running work without stopping the business. We fix it where we found it.
01Branch: cancelled early or cancelled late, every outcome ends in a defined state, never a loop.
02Wire: every branch carries its own requirements and automations.
03Extend: Collections picks up whatever falls through, opened by the failure itself.
04Publish: checked against live work first, then every path runs itself.
We learn the operation before we open an editor. No screen ships without an operational reason.
If the crew won’t use it, it doesn’t work — whatever the backend says.
You pay a fixed price for a finished system. If it takes longer than we planned, we eat the difference.
We automate the tedious work so your people can do the jobs you hired them for.
Every feature earns its keep, or it goes.
We count your pipelines. A pipeline is one record type moving through its full lifecycle: a quote from request to sent, a work order from scheduled to closed, an invoice from drafted to paid. One counts when it has a defined start and end, runs on repeat rather than as a one-off, and more than one person or system touches it on the way through. Reports, one-time projects, and anything the business wouldn’t feel stop don’t count. Ten or fewer, with minimal migration, and you are inside the flat fee: $10,000 total, in three payments. We count them on the scoping call, at no charge, so you know which side of the line you are on before there is an invoice.
Then the package stretches, or the road changes. More extensive migration or additional pipelines can carry the price as high as $30,000 — written into the specification, which you approve before the first payment. Nothing is discovered later. And if there’s a lot you’ll be keeping, the better fit is usually the retainer.
It is arithmetic you can check. Take a twelve-person shop where three people each spend five hours a week copying data between the CRM, the books, and a scheduling tool — roughly $25,000 a year in wages spent retyping what a system should carry itself. Add the subscriptions the new system retires and the jobs that stop falling through, and a $10,000 build repays itself several times in its first year. We run this math with your numbers and put it in the specification, so you approve the return before you approve the fee.
Four to six weeks from first interview to a running system: a week of discovery and specification, a week to design and prototype, a week to build, a week to deploy, and the remainder for revisions while the system takes over. We then stay on call for 30 days from deployment, past the end of the schedule. The schedule assumes your team is available for reviews. The one thing that reliably moves the date is a prototype sitting unread.
You get the source and a perpetual, internal-use license to it. Perpetual means it does not lapse, does not renew, and does not depend on us still being here. You can run it in your business, change it, and hire anyone you like to work on it. You are not locked to us for maintenance. Two restrictions: you cannot resell or redistribute the system, including a version you have modified yourself, and you cannot reverse-engineer the automation engine underneath it. Everything above that engine is yours. The terms are the same at every size; only the pricing differs.
Yes — we design for exactly that. Your automations and backend are emitted as plain TypeScript: no proprietary language, no logic that exists only inside a visual editor, nothing that needs our tooling to open. We organize and name it the way we would want to find it if we were inheriting it cold, and we hold the code to the same standard as the interface. The naming is honest enough that a non-engineer can follow what a file does, and any developer you hire can maintain it without a handover from us. Most clients never need to. The point is that the option is real.
Outside of the package, we work on retainer: a $3,000 monthly minimum, drawn down against hourly work, with the rate quoted on the scoping call. We scope first, quote second, and you approve a written specification before any money moves.
It depends on what we are untangling. A focused automation inside a stack you already run can land in a few weeks. A full ERP architecture with a legacy migration behind it spans months. We deploy in increments, so the first pipeline is earning while the last is still being built, and we do not start without a timeline you have seen.
Not under a standard engagement. That license covers internal operational use. If the goal is to white-label, resell, or ship the deliverable as a product to your own customers, say so during scoping and we will structure a commercial license for it, with a redistribution fee set as a percentage. It is a separate agreement rather than an exception to this one, and it is considerably cheaper to arrange up front than to retrofit.
Often yes, with discipline. We would rather slow down and do it right than chase a trend, and we won’t bolt a large language model onto mission-critical infrastructure where deterministic logic is the safer fit. But the underlying technology has matured into a genuinely powerful tool, with many useful applications: research, classification, drafting, summarization, and any task where recall and speed outweigh strict determinism. Our rule is the same as for any tool we deploy: a clear, measurable path to a return before we implement.
We treat migrations as critical operations. We begin with a parallel testing phase, mapping your existing data structures onto the new architecture and running both side by side. We never “flip the switch” until the new system has been validated against the old one, so the cutover happens without downtime and without losing a record.
We stay on call for 30 days past deployment to fix what breaks. After that the system is yours to run. The license is perpetual, so nothing switches off and nothing needs renewing. We build on our own general-purpose codebase to get you there efficiently and we keep ownership of those foundations, but your license to run and modify what we delivered does not depend on that, or on us. If you would rather keep us, the engagement continues on retainer from $3,000 a month, and you can end it whenever you like.
We are a team of four — two consultants and two engineers — based in Los Angeles, with developers in the United States and Canada. We build for businesses that run on operations: asset-heavy field work, the service trades, and the finance, property, and coordination work around them.
Four is the point. You talk to the people who build your system, the person who interviews your team writes the specification, and nothing is lost in a handoff. Every engagement is scoped in writing and delivered by the people you met on the first call.
The operations we build for:
Two lines on what you run and where it hurts is plenty. We reply within one business day with times — the call is free, and so is the count.
Prefer email? hello@unleadedconsulting.com