Skip to content
Exodus Consulting Exodus Consulting
Book a free audit

Industries / Professional services and agencies

Your firm sells hours, and nobody writes them all down.

A studio of five sells the same thing a firm of five hundred sells: hours and judgement. The hours get recorded from memory on a Friday, the judgement is rarely the bottleneck, and the admin wrapped around both is what eats the margin. We build the systems that record work as it happens and answer the questions that never needed a professional in the first place.

Who this is for

How it actually runs

Before anything is built, this is the week we are describing.

No software can be scoped from a category name. These are the specifics of professional services and agencies that decide what is worth building and what is not.

  1. 01

    Friday timesheets are written from memory

    Work happens all week in calls, email, briefs, drawings and site visits. The timesheet gets filled in at the end of the week by someone who wants to go home. Six minutes here and twenty minutes there never make it in. The firm then bills what was remembered rather than what was done, and that gap does not appear as a line anywhere in the accounts.

  2. 02

    New business arrives by phone and inbox

    A prospect calls once, or sends one email. In a team of six the person best placed to answer is billing at the time, so the call goes to voicemail during the exact hours people call. The email waits two days behind delivery work. Nobody counts the enquiries that went quiet, so the cost of a busy Tuesday morning stays invisible.

  3. 03

    Scope grows by email, never by change order

    The statement of work says one thing. Then the client asks for a small extra round, and it is easier to do it than to raise a change order. Ten of those and the project is thirty hours past the fee that was quoted. The extra work was real, it was done well, and it was never billed, because raising it late feels like starting a fight.

  4. 04

    Launch weeks bend everything around them

    A pitch, a tender close, a filing date, a campaign going live. For two weeks the whole team points at one date and every other client waits. Admin stops, invoices do not go out, and questions that arrive in that window get a short answer or none. The backlog built in those two weeks gets paid for in the quiet month afterwards, at full salary cost.

  5. 05

    Client margin is only known after the job

    The owner knows the fee and roughly knows the effort. Which clients actually pay for themselves is a feeling rather than a number, because hours sit in one tool, invoices in another, and freelancer costs in a folder of PDFs. The unprofitable client is usually the loudest one, and the retainer gets renewed because nobody has put the arithmetic on a page.

Where it leaks

Every one of these is measurable. Most are not measured.

The free audit prices these in your own numbers before anything is scoped. You keep the map whether or not you hire us.

Where the money and the hours go in professional services and agencies, how it is measured today, and what closes it.
The leak How it is measured today What closes it
Billable time that never reaches the timesheet. Not measured. It is the gap between a full day and what appears on Friday. Draft time entries built from calendar, email and file activity, approved by the person who did the work.
Out-of-scope work done as a favour. Noticed at the end of the project, once the fee is already fixed. A scope watcher that flags the overrun in the week it starts, with a change order already drafted.
Finished work sitting unbilled. A month-end scramble through the project system, if anyone has the time. A weekly work in progress list per person, ranked by age and by value.
Enquiries that ring out or wait days for a reply. Not measured at all. A missed call leaves no record anyone reads. A voice agent that answers every call and a chatbot that clears the routine email.

What we build

6 builds that pay for themselves here.

Each one states what it reads, what it does, and what a person still approves. Scope is agreed after the audit, one build at a time, against a baseline you sign.

Voice agent on the main line

It answers every call, including the ones that ring out after five. It reads the project system for status and the calendar for open slots, says where a piece of work is up to, books the call, and takes a new enquiry into a structured record. Anything touching advice, fees or a complaint transfers to a named person with the transcript attached. A person confirms every new project before it opens.

Measured by: Share of inbound calls resolved or booked without a call back.

Website chatbot for the repeat questions

It reads the firm's own published material: how the process works, what a typical timeline looks like, what the client needs to supply, how fees are structured, and the intake form. It answers the low-level questions that currently land in the inbox and hands anything specific to a live project to a person. Every answer cites the page it came from. The owner approves the source set.

Measured by: Inbound emails per week that still need a senior person to reply.

Timesheets drafted from work already done

It reads the calendar, sent email, file edits and call records, groups them by client and project, and writes a draft time entry with a narrative and a duration. The person opens one screen, fixes the wording, deletes what is not billable and approves. Nothing posts to the project system until they do, and unapproved drafts expire instead of piling up.

Measured by: Recorded billable hours per person per week, against the same week last quarter.

Intake and onboarding in one pass

One structured intake record opens the project, runs a conflict and duplicate search across existing clients and related parties, drafts the statement of work from the firm's own template, and creates the folder, the budget and the billing record in each system. The conflict result and the draft both go to a person to clear, and nothing reaches the client until they clear it.

Measured by: Days from first enquiry to signed statement of work.

Scope drift flagged while it is happening

It reads the fee and the deliverables list in the signed statement of work, then watches logged hours, tasks and the email trail against them. When a project passes a threshold the owner sets, or a request arrives that is not on the list, it posts a note with the evidence and a drafted change order. The owner decides whether to raise it, absorb it or write it off.

Measured by: Hours worked past agreed scope each month, and how many of them were billed.

One weekly number pack, every figure sourced

It pulls hours from the project system, invoices and payments from the accounting system, and pipeline from the CRM, reconciles the three, and builds one page: utilisation, billed against worked, unbilled work in progress, receivables ageing and margin per client. Each number carries the system, the query and the timestamp it was read at. Anything that will not reconcile is shown as a gap, not smoothed over.

Measured by: Days of unbilled work in progress, tracked week to week.

The numbers

Borrowed statistics, with their sources and their limits printed.

None of these are our results. They are the published state of professional services and agencies, linked so you can check them, with the caveat attached where the number is a survey, a forecast or a vendor's own figure.

73.8%

Nearly three quarters of professional services employers in Canada have fewer than five staff.

Innovation, Science and Economic Development Canada, using a Statistics Canada special tabulation, 2025

Employer establishments only. The 372,200 non-employer or indeterminate establishments in the same sector sit outside this share. Unpublished Statistics Canada tabulation, unclassified establishments excluded.

65.6%

Professional services has the highest rate of generative AI use at work of any Canadian industry.

Statistics Canada, 2026

Self reported by workers in a March 2026 survey. It counts any use of a generative AI tool at work and says nothing about whether that use was sanctioned, governed or paid for itself.

38%

In an eight hour day, hourly professional work averages three billable hours recorded.

Clio, 2025

Vendor reported, and law firms specifically. Clio aggregates anonymised data from firms using its own practice management software across North America, so it is not a Canadian government figure and not a benchmark for agencies. It is quoted here as the closest published measure of how much of a professional day is captured as billable.

Where the data comes from

Your systems of record stay exactly where they are.

We read them, we do not replace them. Each one below says what we connect to, how, and the line the build does not cross.

Project, time and resource management

Usually: Productive.io, Scoro, Workamajig, Harvest, Float, Deltek Vantagepoint, BQE Core, Monograph, Asana, Monday.com, ClickUp

What it holds. Projects and phases, time entries, tasks, budgets, staff allocation, freelancer bookings and the fee agreed per engagement.

How we connect. Read through the vendor API where one exists, otherwise a scheduled export into a read-only copy we keep in sync. Anything we write back goes in as a draft time entry or a draft task.

Where it stops. No time entry is posted, no budget changed and no project closed without a person approving it inside the tool they already use every day.

Accounting, invoicing and payments

Usually: QuickBooks Online, Xero, Sage 50, Dext, Plooto, Wagepoint

What it holds. Invoices, work in progress, disbursements, supplier and freelancer bills, receivables ageing and the general ledger.

How we connect. Read-only API access plus webhooks on invoice and payment events. We reconcile against the project system on a schedule and record every mismatch with a confidence score rather than picking a winner.

Where it stops. We never issue an invoice, apply a credit or move money. The system prepares the batch and shows the arithmetic. The bookkeeper and the owner send it.

CRM, email and file stores

Usually: HubSpot, Salesforce, Pipedrive, Microsoft 365 and SharePoint, Google Workspace, Dropbox, Notion

What it holds. Enquiries, pipeline stages, the email trail with each client, proposals, statements of work, deliverables and version history.

How we connect. API and webhook on new enquiry and new message. Files are read only where permissions already allow it, indexed per client, and never copied outside the firm's own tenancy.

Where it stops. Nothing goes to a client from these systems on its own. Drafts land in the account lead's own drafts folder, and they press send.

Built around your rules

The regimes that govern this work, and how the build answers each one.

Constraints come first, because they decide the architecture. Bring us your hosting, residency and regulatory rules at the start and we design to them rather than around them.

Regulatory and professional obligations that shape a build in professional services and agencies.
Regime What it demands here How the build complies
PIPEDA Consent, a stated purpose for each piece of personal information collected, limits on how long it is kept, and reporting a breach to the Privacy Commissioner where there is a real risk of significant harm. Each field is mapped to the purpose it was collected for and access is set by role. Retention and deletion run on a schedule. Every read of a client record is logged, so a breach can be scoped in hours rather than weeks.
BC PIPA, Alberta PIPA and Quebec Law 25 Provincial private sector privacy rules on top of the federal ones. Law 25 adds a named privacy officer, privacy impact assessments before a new system goes in, and disclosure when personal information is transferred outside Quebec. Hosting location is decided before the build rather than patched in after. Canadian hosting is the default and we can hold data in a specific region where a firm needs it. The assessment is written down and handed to the client.
CASL Consent before a commercial electronic message, a clearly identified sender with contact details, and a working unsubscribe honoured within ten business days. Consent type and the date and source it came from sit on every contact record. Anything without valid consent is excluded from a send. An unsubscribe writes back to every connected system at once, not just the one it arrived in.
Professional regulators and client confidentiality Provincial CPA bodies, law societies and regulators such as Engineers and Geoscientists BC require client confidentiality, conflict checks and records that can be produced on request. Client NDAs and master services agreements usually add their own limits on where data may sit. Client data stays inside the firm's own tenancy. A conflict search produces a result a person clears rather than an automatic pass. Every automated action writes an audit line naming who approved it and when.

What we will not automate

  • We do not let a model give a client professional advice. It answers process and status questions and hands anything needing judgement to the person who carries the licence and the liability.
  • We do not automate a conflict clearance, a write-off, or an invoice going out the door. The system runs the search and drafts the number. A person signs it.

A person stays in the loop

Anything that spends money, sends something irreversible, or carries a professional obligation arrives as a draft with a named reviewer. The system prepares the work. A person decides whether it ships.

You own the code and the data at the end of the engagement.

Questions

The questions we get asked in professional services and agencies.

Because this one writes the entry for them. The draft is built from the calendar, the sent email and the files they touched, so the job changes from remembering a whole week to editing a list. It takes minutes instead of an hour, and nothing posts until they approve it. If they ignore it, the drafts expire rather than becoming another backlog.

It is built to sound like your office and to hand over quickly. It covers status, availability, what a client needs to send, directions and booking a call. The moment someone asks a question that needs judgement, or sounds unhappy, it transfers to a named person with the transcript so nobody repeats themselves. You set what it may answer and you hear the recordings.

Yes. Nearly three quarters of professional services employers in Canada have fewer than five staff, and that is the shape of business we build for. The work is scoped to one or two builds that pay for themselves, not a platform. We agree the number we are aiming at in writing first, and if the system misses it we keep working at no extra cost until it clears.

Yes, and often they have to, because a client contract or a regulator says so. We treat hosting as a constraint decided before the first line of code rather than a setting changed later. Canadian hosting is the default, and we can hold the data in a named region where an agreement requires it. Every model and every byte stays where you say it stays. You own the code at the end of it.

What happens next

Start with the audit, and know the number before you commit.

Three to five days. We map where the hours and the money go in your professional services and agencies operation and hand you a ranked plan with the payback attached.

We map where time and money leak, and show the arithmetic before you commit to anything. You keep the map whether or not you hire us. If we do build, we agree the baseline in writing first, the clock starts at deployment rather than signature, and you own the code.

Who you talk to
Shiv and Vishal. No account managers, no slide decks.
Direct
shiv@exdsconsulting.com
Read next
What we build, then Our work.