Running an IT services business on a CRM
IT services engagements run on estimates, SOWs, and milestone billing — not a lead list. Here's how to set up a CRM around that reality, stage by stage.
9 min read9 steps
Why a spreadsheet stops working past a handful of clients
An IT services engagement isn't a single deal — it's a chain of documents and dates: a scoped estimate, a signed SOW, a string of delivery milestones, the change orders that inevitably follow, and an AMC renewal a year later. A spreadsheet can hold a list of clients, but it can't tell you which SOW is still unsigned, which milestone invoice is overdue, or which AMC renews next month. Once you're running more than a handful of engagements at once, that gap is where revenue quietly leaks.
The IT services engagement, stage by stage
Every IT services engagement — a website build, an app, ongoing support — moves through the same shape. Naming the stages is what makes them trackable.
Enquiry
A prospect reaches out about a project or support need. The first job is just capturing it in one place — not a forwarded email, an actual record with a source and an owner.
Requirement gathering
You scope what they actually need through calls and documents. This is where most detail gets lost if it lives in someone's inbox instead of on the record.
Estimate
A ballpark cost and timeline goes back to the client, based on the gathered requirements.
Proposal / SOW drafted
The estimate becomes a formal statement of work — scope, deliverables, milestones, and payment terms spelled out.
Negotiation
Scope or price gets adjusted. Every revision should update the same SOW record, not fork into a new email thread.
Signed SOW
Client signs off. This is the point work should be authorized to start — and the point the payment schedule locks in.
Delivery milestones
Work is delivered against the milestones in the SOW, each one triggering its own invoice.
Change orders
Scope changes mid-project get logged as their own record, linked to the original SOW — not absorbed silently into the timeline.
AMC renewal
Once delivered, the engagement moves into an annual maintenance contract that needs its own renewal reminder months in advance.
Where IT services engagements usually go wrong
These aren't hypothetical — they're the same handful of failure points that show up across most IT services teams before they centralize on a CRM.
Change orders agreed over chat, never documented
A client asks for 'one small addition' on a call, it gets built, and six months later nobody can point to when scope — or price — actually changed.
Requirements live in someone's notebook or inbox
The person who ran discovery leaves or gets busy, and the only record of what was actually promised leaves with them.
AMC renewals get missed
Without a reminder tied to the contract date, an annual maintenance contract lapses quietly — and the client finds out when something breaks.
Invoicing is disconnected from delivery
Milestones get delivered but the corresponding invoice is a manual, easy-to-forget step instead of a triggered one.
What to set up before you go live
The workflow above only works if the CRM is configured to match it, not a generic sales pipeline you're forcing your process into.
What Worxley adds on top of this workflow
You can build the process above in any CRM that lets you customize pipelines and fields. Worxley was built with IT services engagements specifically in mind — the SOW-and-milestone shape is a first-class fit, not a workaround.
- Configurable pipelines
- Set up the exact nine stages above — or fewer — without fighting a fixed sales-funnel structure.
- E-signature built in
- Send, sign, and track SOWs without leaving the record or paying for a separate e-signature tool.
- Milestone & AMC reminders
- Automated nudges before a milestone invoice or AMC renewal is due, not after it's already late.
- Client transparency mode
- Give a client visibility into their own engagement status without giving them access to your whole CRM.
FAQ
A ticketing tool tracks issues after a client is live. This covers everything before that — enquiry, scoping, SOW, and delivery — plus the AMC that eventually links the two. Most teams run both, connected by the same client record.
Log each change order as its own linked record against the original SOW, with its own value and sign-off — so the engagement's real scope and price are always the sum of what's actually on file, not what anyone remembers agreeing to.
Yes — set a renewal date field on the engagement and a reminder rule fires a set number of days before it, to the account owner, without anyone maintaining a separate calendar.
Most teams import their existing client list as a starting point, then rebuild the pipeline stages to match the workflow above going forward. You don't need historical SOWs migrated to get value from tracking new ones properly.
Keep reading
You've seen how it works on paper. Now set it up for real.
Use the pipeline from this guide as your starting point, and adjust it to your business.