Which should you automate first: the phone, the CRM, or the reports?
Not an opinion. Three requests documents, two of them kept as the requests arrived and the third reconstructed from commit history, read in date order.
By Eugene Romanov·Published
The short answer
The records, every time, and three requests documents say so rather than an opinion. Across a wallpaper contracting company, a car brokerage and a sauna builder, the first thing each asked for was the record: an invoice that would not send, the arithmetic behind a profit figure, an estimate built from their own calculator. The phone came fourth or never. Reports arrived as a doubt about numbers, not as a request.
SHT-02What drives the number
Where this answer comes from, and why it is not an opinion
Every client-facing project here keeps a requests document: one line per request, its state, and the commit that delivered it. Three exist, one per system, and they were written to answer was this built rather than to make an argument, which is what makes them usable at all. They differ in how they were made, and that decides how much each is worth. The car brokerage list and the sauna builder list are kept as the requests arrive, the second of them reconstructed back to its fork for the period before that habit started. The wallpaper contracting list is a reconstruction throughout, assembled from commit history in September because nobody had been keeping one, and it says so at its head. The rows and the dates are real in all three; only the third has its sequence from commit order rather than from a note taken at the time.
The wallpaper contracting company asked only about screens and documents
Every recorded request from that customer concerns the record or a document coming out of it. The earliest is an invoice that could not be received, where the send button flipped a status and emailed nothing at all. Then: let estimates move through the board without being calculated first, an area switched off was still being charged for, on the printed sheet the room name and the yardage ran together, people were being signed out every couple of hours, and a bare calculator widget to embed elsewhere. Not one request about the phone. Not one request for a report. This is a business with paying work coming in, and every ask is about the thing that holds the work.
The car brokerage began with the arithmetic, which is the reporting question in work clothes
The earliest dated block in that document, which lists newest first, is the money model: expenses with a name and an amount on the dashboard, what profit means once the dealer and every cost come off, percentages resolving against the actual profit after deductions, and more report categories, owed by us, owed to us, all spend, all income. That is the reporting layer, asked for on day one, because in that trade the number is the product. A later entry is not a request for a new report at all but a doubt, the figures feel wrong, show me the whole arithmetic of the dashboard. Nothing anywhere in that document asks for telephony.
The sauna builder's proposal had nine points and the phone was not one of them
The nine: an estimate built from his own calculator, sequential numbering so a previous total cannot land in a new estimate, inventory inside the estimate with stock deducted on approval, projects and people in one list, a calendar with an installer assigned and payouts, a client portal showing progress and signed documents, intake from his own website feeding the system, an invoice generated from the estimate with no retyping, and a PDF in his branding. Telephony arrived later, after the deposits work and after the planner, and the fuller version of it is the first of five items in the package quoted after those rather than a project of its own. It still waits on things outside the code: a number to buy, a legal entity for message registration, and a decision about recording calls in a two-party-consent state.
Reports do not arrive as a request. They arrive as a doubt
In two of the three documents the reporting entry is somebody saying the numbers feel wrong, or a question that blocks reporting until it is answered. Nobody asked for a dashboard. They asked why two screens disagreed, or whether every closed job had reached the invoice file at all. That tells you when the reporting work is worth doing: not at the start, when there is nothing yet to report on, and not last either, but at the moment the owner stops trusting a figure. Build it earlier and you are reporting on records nobody has stress-tested. Build it later and the owner has already started a private spreadsheet, so now there are two answers again.
The order, the two exceptions, and when to do none of it
For a trade that quotes and invoices, which is most of them, the evidence gives records first, then reporting at the moment a number is first doubted, then the phone once you can count what the phone is losing. Two exceptions are worth naming. If work arrives almost entirely by phone and you can count last month's unanswered calls, the phone is first and that arithmetic is yours to do this afternoon. If your money depends on one calculation, as it does in brokerage, the arithmetic and the reporting on it are the same job and come together at the front. And do none of it if you cannot yet say which of the three is costing you: the free audit is same day and costs nothing.
SHT-03The options, side by side
What each route actually costs you.
| Option | Price | Timeline | The trade-off |
|---|---|---|---|
| The records, meaning a CRM | Custom CRM from $2,000 over 30 to 45 days, or the subscription at $99 a month for Pro and $199 a month for Team | 30 to 45 days to build, or 1 to 2 weeks to fit an existing system | Nothing downstream works without it and it is the slowest to feel exciting. Every request in all three documents was ultimately about this layer. |
| The reports | Usually retainer work once the records are in one system: $300, $750 or $1,500 a month | Days, on top of records that already exist | Cheap and quick when the records are clean. Reporting on records nobody trusts is worse than no reporting, because it converts doubt into false confidence. |
| The phone | Inside a custom CRM from $2,000 over 30 to 45 days, plus carrier and model usage on your own accounts | 30 to 45 days, plus registration time you do not control | The only one whose loss you can count before buying. Also the only one gated by paperwork: numbers, message registration, and call-recording law in your state. |
| None of the three, yet | $0 | Same day | The free audit, plus your own count of last month's missed calls and dead quotes. If that arithmetic is small, keeping the money is the right answer. |
SHT-04In this hub
Roofing websites that book emergency calls.
Storm-season-ready roofing websites built for South Florida contractors. Insurance-claim walkthrough, 24/7 call band, lead form wired to the owner's phone.
Plumber websites that turn 2am calls into booked jobs.
24/7 emergency plumbing websites for South Florida shops. Click-to-call on every section, quote form wired to the owner's phone, transparent pricing band.
HVAC websites that close service calls in 90° heat.
South Florida HVAC websites built for July. Same-day service CTA, financing inline, maintenance plan opt-in, FL CAC license front-and-center.
Cleaning service websites that book recurring appointments.
Residential and commercial cleaning websites for South Florida. Online booking, recurring-plan signup, transparent per-visit pricing, lead form to your phone.
Pressure washing websites that book the whole driveway.
South Florida pressure washing sites with photo proof, square-foot pricing, and one-tap booking. Lead form wired to your phone.
Auto detailing websites that book the package upgrade.
South Florida auto detailing sites with package tiers, mobile-detailing routing, ceramic coating add-ons, and transparent pricing.
Dental practice websites that book new patients.
South Florida dental practice websites with $99 new patient offer, evening hours surfaced, insurance explainer, and online booking.
Med spa websites that turn an expensive click into a booked consult.
South Florida med spa websites with treatment menus, before/after galleries, package pricing, and online booking. Built for high-AOV conversions.
Contractor websites that get past insurance gatekeepers.
South Florida general contractor websites with FL CGC license proof, insurance verification, project gallery, and quote-request form.
Realtor websites that book listing appointments.
South Florida realtor websites with neighborhood pages, listing search, valuation form, and seller-focused content.
What a contractor's CRM has to model that generic software does not
A sales CRM models a deal moving toward a signature. A contractor's job carries on for weeks after the signature, and that is where the money is decided.
CRM for auto brokers: what belongs inside one
A broker does not sell a car off a lot. He finds the car across a network of dealers and gets the buyer financed, and whether he earns anything is decided by a credit application.
CRM for custom sauna builders: pricing a room that does not exist yet
The estimate is a drawing and a price at the same time, and the price has to follow the drawing while the client is still watching.
CRM for wallpaper installers: the arithmetic no generic CRM does
Every trade has one calculation that decides whether the job made money. In wallpaper it is the roll count, and it is not the room area divided by the roll area.
SHT-05General notes
The questions people actually ask.
- N01Should I automate the phone, the CRM or the reports first?
- The CRM, in almost every trade, and three requests documents kept during real builds say so rather than an opinion. All three clients opened with the record: an invoice that would not send, the arithmetic behind a profit figure, an estimate built from their own calculator. Reports and telephony came later or not at all.
- N02When is the phone the right thing to do first?
- When work arrives almost entirely by phone and you can count last month's unanswered calls. That count times what a booked job is worth to you is the only figure in this decision that belongs to your business, and if it is large the phone stops being third.
- N03Why did none of your clients ask for reports up front?
- Because reporting does not present itself as a feature request. In two of the three documents the reporting entry is a doubt, the figures feel wrong, show me the arithmetic, or a question about whether closed jobs reach the invoice file. The right moment to build it is when the owner stops trusting a number.
- N04Why is telephony usually last?
- Because most of it is not code. A number has to be bought, business messaging needs registration behind a real legal entity, and whether calls may be recorded depends on the state you operate in. In one build the telephony was written and then waited on exactly those things, which is a delay no developer can shorten.
- N05Does the order change by trade?
- Only in two cases. If your money hangs on a single calculation, as in brokerage, the arithmetic and its reporting are the same job and come first together. If your leads arrive by phone and nothing else, the phone moves up. For quote-and-invoice trades such as contracting, installation and build work, records come first.
- N06How long does each of the three take?
- A custom CRM is 30 to 45 days from $2,000, or 1 to 2 weeks to fit the existing system on a subscription. Reporting on top of clean records is days and is usually retainer work at $300, $750 or $1,500 a month. Telephony is build time plus registration time you do not control.
- N07What if I cannot decide?
- Do none of them and count instead. Last month's unanswered calls, quotes that got no second message, and hours spent retyping figures between tools. Whichever count is biggest names your first project, and the free audit is a same-day walkthrough that costs nothing and will say the same thing in your own numbers.
SHT-06Evidence
The systems this argument comes from.
Everything above was learned building these. Each sheet names the business, what the trade's arithmetic actually is, and the file in the repository that proves the capability. No client revenue and no client's customers appear on any of them.