Saltar al contenido
A custom CRM + ERP runs lead, quote, job, invoice and payment in one system you own. It costs a fixed build fee plus hosting, and it beats subscriptions once you pay for four or more tools that do not talk.
2026-10-07 Justin CowellCommand SystemCRMERPØrigin 1.0 Todos los informes

A custom CRM + ERP for a service business is one system that carries a customer from first inquiry to paid invoice without anyone retyping anything, and that you own outright instead of renting seat by seat. It costs a fixed build fee, quoted after a free audit as part of our Mission BRAVO, then run with you every month on HyperCare+, and it beats a stack of subscriptions when you are paying for four or more tools that do not talk to each other.

This post explains what the system contains, what our Ørigin 1.0 architecture standardizes so that the build takes six weeks rather than six months, what the costs look like against a typical subscription stack, and the cases where you should not build at all.

Lead to paid in one system

The core of the system is a single record that changes state: a lead becomes a quote, the quote becomes a job, the job becomes an invoice, the invoice becomes a payment. Every person in the business sees the same record at every stage, and the data entered once at the start is still there at the end.

That sentence sounds obvious until you compare it with how most service businesses actually run. A lead arrives by phone and is written on a pad. It is typed into a CRM. The quote is built in a separate estimating tool, with the address typed again. The accepted quote becomes a job in a scheduling app, typed again. The completed job becomes an invoice in the accounting package, typed again. Payment arrives through a card processor, and someone reconciles it by hand on Friday. Five tools, five logins, and the same customer's name entered five times, with a different spelling in two of them.

The one-system version looks like this.

Lead. An inquiry arrives from the website form, a phone call, a text, or a referral. It lands in a pipeline with a source, a timestamp, and an owner. If nobody responds within the window you set, it escalates. We wrote about why that window matters in the follow-up gap.

Quote. The quote is built from your own price book, with your margins, on the lead's record. It is sent as a link the customer can accept on their phone. Acceptance is recorded, with a time, against the record.

Job. Acceptance creates the job with the scope from the quote, assigns a crew, and places it on the calendar. The crew sees the job on their phones with the address, the scope, the notes, and the photos. They record time, materials, and completion photos on the same record.

Invoice. Completion generates the invoice from the quote and the actual materials used. Variations are visible as variations, not as a mystery difference between two numbers in two systems.

Paid. The invoice carries a payment link. Payment is recorded on the record, the accounting system receives the entry, and the job is closed. If payment does not arrive, the reminder sequence starts without anyone remembering to send it.

Reporting falls out of this structure for free. Because every stage is a state on one record, the business can answer "what is our quote-to-job rate by source," "which crew runs over on time," and "how long does a customer take to pay" without exporting anything. Those are the questions a stack of subscriptions cannot answer, because the answer lives in three of them.

The client portal and rewards

The client portal is the customer's view of the same record: their quotes, their scheduled jobs, their invoices, their payment history, and a place to ask a question that reaches the right person. Rewards sit on top of it, so that a referral or a repeat booking is tracked and credited automatically rather than remembered.

The portal does two commercial jobs. It removes the "where is my invoice" and "what time are you coming" calls that take up a surprising share of an office manager's day, and it gives the customer a reason to come back to your brand rather than search again. A customer who can rebook a service in two taps does not go looking for a competitor.

Rewards work because the data is already there. A referral credit needs to know who referred whom, whether the referred job completed, and what it was worth; a loyalty discount needs to know how many jobs a customer has had. In a subscription stack this needs a sixth tool and a spreadsheet. In one system it is a rule.

What the portal looks like depends on the business. A tree service shows the quote, the scheduled date, and the completion photos. A coaching business shows the program, the sessions, and the resources. A hardscape contractor shows the design, the stage payments, and the progress photos. The industries page sets out the patterns we have built for each.

What Ørigin 1.0 standardizes

Ørigin 1.0 is our architecture for these systems. It standardizes the parts that are the same in every service business so that the build effort goes into the parts that are different. About 70 percent of any Command System is standard; the remaining 30 percent is yours.

The standard parts:

  • The data model. Contacts, organizations, properties (the site where the work happens, which is often not the customer's address), leads, quotes, jobs, line items, invoices, payments, and documents, with the relationships between them already defined. Every service business needs these; none of them need to be designed from scratch.
  • The pipeline engine. State changes, who can trigger them, what happens when they occur, and the audit trail that records them. The rule "a quote cannot become a job until it is accepted" is a configuration, not a feature request.
  • Roles and permissions. Owner, office, crew lead, crew, accountant, and customer, with sensible defaults for what each can see and change.
  • Notifications. Email and SMS templates for every state change, with the timing and the escalation rules exposed as settings.
  • The portal shell. Login, the record views, payment, messaging, and rewards, themed to your brand.
  • Reporting. The standard questions, answered on a dashboard, with the data exported to a spreadsheet in one click.
  • Integrations. The connectors to payments, calendar, messaging, and accounting, described below.

The custom parts are your price book and quoting logic, your job types and the fields each one needs, your crew structure and scheduling rules, your documents (quotes, invoices, certificates, reports) with your layout and wording, your portal views, and any workflow specific to your trade: a pre-job safety checklist, a permit tracker, a stage-payment schedule, a warranty register.

Standardizing the first list is what makes the six-week timeline honest. It is also what keeps the system maintainable, because every Ørigin system shares the same foundation and a fix made to that foundation reaches every client on it.

Integrations

The system connects to four things you already use: your payment processor, your calendar, your messaging channels, and your accounting package. It does not replace them, because the versions you already have are good at their jobs; it removes the retyping between them.

Payments. Quotes and invoices carry a payment link from your existing processor (Stripe, Square, or a regional equivalent such as GoCardless for UK direct debit or Mollie in the Netherlands). Payment status updates the record automatically. The system never stores card details; that stays with the processor, which is built and audited for it.

Calendar. Jobs appear on the crew's calendar (Google or Microsoft) and changes flow both ways, so that a job moved in the field moves in the office.

SMS and email. Confirmations, reminders, on-the-way messages, review requests, and payment chasers go out from the system, through a messaging provider in the customer's country so that the number and the sender name look local. Replies come back onto the record.

Accounting. Invoices and payments post to QuickBooks, Xero, Sage, MYOB, or whatever your accountant works in, so that the accounting package remains the ledger of record and your accountant never has to learn a new tool. We hold the operational data; they hold the books.

Each connector is standard in Ørigin, so adding one is configuration rather than development. If you use a tool we have not connected before, that is part of the custom 30 percent, and we say so before the build begins.

Security and roles

Security in a custom system is a design decision you make once, rather than a setting you hope each vendor has made. The system is built against the OWASP Top Ten (OWASP), runs over HTTPS only, encrypts data at rest, and keeps an audit log of every change to every record with who made it and when.

Roles are where most of the practical security lives. A crew member sees today's jobs and the fields they need, not the customer's full history or the margin on the quote. The office sees everything operational but not the owner's reporting. The accountant sees invoices and payments and nothing about the pipeline. A customer sees their own records and no one else's. Every one of those boundaries is enforced by the system, not by trust.

Access is by named user with two-factor authentication, and when someone leaves, one switch removes them from everything at once. Compare that with the subscription stack, where offboarding a departing office manager means remembering five logins, two of which were shared.

Data residency matters for businesses outside the United States, and it is a question you can answer with a custom system. If your customers are in the EU, the data can live in the EU. If you are in Australia, it can live in Australia. A subscription vendor decides that for you.

Backups run daily, are tested, and are restorable by us within hours. This is part of what HyperCare+ covers every month.

The six-week build

The build takes six weeks from a completed intake to a live system, in six stages of roughly a week each. The stages are fixed; the work inside them is what varies by business.

Week 1: Discovery. We sit with the owner and the office and map how a customer actually moves through the business today, including the parts that live on paper and in someone's head. The output is a written description of the current process and the target process, with every field and every document named.

Week 2: Blueprint. The data model, the pipeline states, the roles, the documents, the integrations, and the portal views are written down and signed off. This is the last cheap place to change your mind.

Week 3: Build. The standard Ørigin foundation is deployed and the custom 30 percent is built on it: your price book, your job types, your documents, your workflows.

Week 4: Wire-up. Payments, calendar, messaging, and accounting are connected and tested with real transactions in a sandbox. Your existing customer list and open jobs are imported and checked.

Week 5: Secure and test. Roles are verified field by field. The team runs a week of real jobs through the system in parallel with the old process. Everything that feels wrong is fixed, and the training for each role is recorded.

Week 6: Launch. The old tools are switched off in an agreed order, the subscriptions are cancelled, and the system goes live with us watching it for the first fortnight.

If the system is part of a full rebuild with a new website, it ships inside a mission, and the whole mission carries our launch guarantee: live within 45 days of a completed intake, or the first three months of HyperCare+ are free.

Owning versus renting

You own the system: the code, the data, the hosting account, and the right to take it elsewhere. A subscription gives you a license to use someone else's system for as long as you keep paying, on terms they can change.

The practical differences show up in four places.

Price changes. A subscription vendor can raise the per-seat price, move a feature you depend on into a higher tier, or add a usage charge. You find out by email. A system you own has one monthly cost for hosting and maintenance, and it does not change because the vendor raised money.

Features. A subscription has the features its largest customers asked for. A system you own has the features you asked for, and adding one is a conversation with us rather than a vote on a feedback board.

Data. Your data in a subscription is exportable in the format the vendor allows, which is usually a spreadsheet without the relationships. Your data in a system you own is a database you can query, back up, and move.

Exit. If you sell the business, the system is an asset that transfers with it. A subscription is a liability the buyer inherits.

Renting is the right choice for some businesses, and we cover that below. But the arithmetic of renting changes once you have several seats on several tools, and most owners have never done it.

A worked example

Take an invented five-truck heating and air company in Christchurch, New Zealand, with an owner, an office manager, a part-time bookkeeper, and eight field staff. The numbers below are the company's own invoices, invented for the example; your figures will differ, and the point is the method rather than the totals.

Its stack: a CRM at $45 a month per seat for three office users ($135), a quoting and job-management app at $60 a month per user for eleven users ($660), a scheduling and dispatch add-on ($120), an SMS reminder service ($50), a review-request tool ($40), a form builder and automation tool connecting them ($70), and e-signature for quotes ($35). The accounting package and the payment processor stay in both scenarios, so they are left out.

That is $1,110 a month, or $13,320 a year, before the renewal-time increases that arrive most years. It is also seven logins, seven places a customer's name can be misspelled, and an office manager who spends part of every day moving information between them.

The custom system replaces all seven. The build is a one-time fee, quoted after a free audit as Mission BRAVO, which also includes the website, and there are no per-seat fees after it, however many people you hire.

Over three years, the subscription stack costs about $40,000 if prices never rise, and at the end the company owns nothing. The custom system is a one-time build the company owns outright. Running it with us on HyperCare+ (quoted to your footprint) is a separate choice, and it covers far more than software: search, posts, email, reviews and reporting, done for you or by you.

The savings that do not appear on an invoice are larger. Each job requires one entry rather than four. Quotes go out the same day because the office is not switching between tools. Payment reminders go out on time, every time, which shortens the gap between finishing a job and being paid. None of those appear in the subscription comparison, and all of them are the reason owners say the system paid for itself before the first renewal they did not have to pay.

When not to build

Do not build a custom system if you are a one-person business, if your process changes every month, or if a single off-the-shelf tool genuinely does everything you need for a price you are happy with. In those cases a build is money spent to solve a problem you do not have.

The specific cases:

  • You are the only user. A solo operator with a phone, a calendar, and an invoicing app is already running one system. Build when the second office person arrives.
  • The process is not settled. A custom system encodes how you work. If you do not yet know how you work, because the business is six months old or is changing its model, encode it later. Use a cheap subscription for a year and take notes.
  • One tool already fits. Some trades have a dominant platform that does the whole lead-to-paid flow well. If you are on it, you are using every part of it, and the price is acceptable, stay. The case for building begins when you are paying for a second tool to cover the first one's gaps.
  • You will not use it. A system is a habit. If the owner intends to keep quoting on paper and the crew intends to keep texting the office, the system will be accurate for a week. We have turned down builds on this basis and will again. We wrote about the pattern in six apps, one you use.
  • The budget is better spent elsewhere. If your website does not bring in leads, a system to manage leads is the second purchase, not the first.If you want to know where you stand first, book a call and we will walk through your site, listings and search with you.

What to do next

If you suspect you are paying for too many tools, the work this quarter is to find out rather than to guess.

  1. List every software subscription the business pays for, with the monthly cost, the number of seats, and the renewal date. Most owners are surprised by the total.
  2. Follow one customer through the business on paper, from first contact to payment, and count how many times their details are typed and how many tools are opened.
  3. Write down the three questions about the business you cannot currently answer without a spreadsheet.
  4. Decide whether the honest answer is "one tool, used properly," "keep renting for a year," or "build."

If it is the last, the Command System ships on its own or inside a mission, and the full description of what it contains is on the systems page. The first conversation is a 30-minute discovery call, and if we think you should not build, we will say so in that call.

Preguntas de este informe

Si esto describe tu negocio, una llamada te mostrará qué parte te está costando más.