The call you would book with a business process automation consultant, answered before you book it
Every consultancy that ranks for this term gates a free discovery call behind a button, then quotes a recurring automated routine that lives in a tenant you do not own. This page walks the questions that call would ask, shows the routine they would build, and lets you decide whether you need a paid engagement or a tool you run yourself.
Direct answer · verified 2026-06-16
Yes, you can book a call. Firms like Quantzig, K3 Techs, Wakeflow, and BoostedCRM put a free discovery call behind their "book a call" button, and that call leads to a paid build (commonly $5k to $40k) plus a retainer. Fazm offers a free 30-minute scoping call too, at cal.com/team/mediar/fazm, but Fazm is a free, open-source macOS tool that runs the recurring routine yourself, not an hourly engagement. Book the Fazm call to check fit; you may leave with a routine you set up rather than a proposal.
What the discovery call is really measuring
A discovery call is the consultant's qualification step. They are not designing your automation on that call; they are sizing the engagement. The whole conversation reduces to three measurements, and you can take them yourself in fifteen minutes. The answers decide whether your process is a self-serve routine or a real consulting project.
App count
How many apps does the process touch, and do any of them lack a usable API? Five or fewer, all reachable on screen, is self-serve territory.
Operator count
How many people run it today and how often? One or two operators on a daily or weekly cadence is a routine, not a transformation.
Audit risk
Does the output need to be signed or audited for SOX, HIPAA, or SOC 2? If yes, you need a named human owner, and that is where a consultant earns the fee.
Rule of thumb: if app count is five or fewer, operator count is two or fewer, and audit risk is low, the deliverable is a routine you can own. If any of those break, the call is worth booking with a human.
What actually gets built after you book the call
1. Discovery call, free
The anchor fact: a routine is a row in cron_jobs
This is the mechanism the consulting pages cannot show you, because their deliverable lives in a tenant you do not control. In Fazm, a recurring routine is a row in a SQLite table called cron_jobs, created in database migration fazmV7 (Desktop/Sources/AppDatabase.swift). A headless runner at acp-bridge/cron-runner.mjs fires it on your Mac and writes one row per run to a cron_runs log.
// The schedule column carries one of three formats:
// "cron:<expr>" 5-field cron, e.g. "0 9 * * 1-5" (weekdays 9am)
// "every:<sec>" fixed interval
// "at:<iso8601>" one-shot
try db.create(table: "cron_jobs") { t in
t.column("name", .text).notNull()
t.column("prompt", .text).notNull() // the process, in English
t.column("schedule", .text).notNull()
t.column("enabled", .boolean).defaults(to: true)
t.column("next_run_at",.double)
t.column("last_status",.text) // "ok" | "error"
t.column("run_count", .integer).defaults(to: 0)
}
// One row per fire, with the line consultants never show you:
try db.create(table: "cron_runs") { t in
t.column("status", .text).notNull() // ok | error | timeout
t.column("output_text",.text)
t.column("cost_usd", .double) // what THIS run cost
}Two details a consultant proposal will not give you. First, the prompt column is the process described in plain English, so the routine is readable and editable by you, not a graph locked in a vendor UI. Second, the cost_usd column means every automated run has an itemized cost on your own machine. A flat retainer hides that line; here you read it.
Schedule formats: cron, interval, one-shot
A routine is one row in cron_jobs
Vendor accounts required to own it
Free Fazm scoping call
How a routine reaches apps that have no API
The reason a consultant's custom build is expensive is that real back-office processes touch apps with no clean API. Fazm gets there a different way: the same routine drives your real macOS apps and browser through the accessibility tree, the primitive VoiceOver uses to read the screen, rather than a brittle endpoint or a screenshot model.
A recurring process, end to end, on your Mac
Processes Fazm has already run end to end
These are the order-processing, fulfilment, finance, and document tasks that consultancies like Quantzig list as their core engagements. The Fazm repo carries captured runs of each, driven through the accessibility tree against the live app.
Marketplace order and message handling
Open the eBay seller hub, read a buyer message, draft a reply, and update an order. Captured across the seller inbox, order, and reply screens.
Shipping claims
Fill and submit a UPS claim form end to end, including the guest-claim path, across multiple form steps.
Finance: wire review
Walk a Mercury wire review screen and a Stripe checkout, the invoicing-and-payments work consultants quote as a standalone build.
Contract editing in Google Docs
Find-and-replace clauses in a Google Doc: an MSA section swap, a mutual-release edit, a non-disparagement rewrite, with undo verification.
Document workflows
Handle a password-protected PDF, preview a Gmail attachment, and generate files via the pdf, docx, xlsx, and pptx skills.
CRM data entry
Keep a CRM current by reading context off the screen and entering updates, the recurring data-entry task most retainers cover.
Each of these is a workflow a consultant would scope as its own line item. As a Fazm routine, it is one row in cron_jobs with a schedule.
Apps these routines drive through the accessibility tree
Anything VoiceOver can read, a routine can drive. That is why a single accessibility primitive covers a marketplace inbox, a shipping form, and a contract edit alike, with no per-app integration to license.
The booked engagement vs the routine you own
This is not a claim that consultants are obsolete. It is a claim that the default SMB engagement (discovery call, custom build, retainer) produces a recurring routine you rent, and Fazm produces the same kind of routine, owned, for the slice of processes that fit the three measurements above.
What you walk away with
| Feature | Consultant engagement | Fazm routine |
|---|---|---|
| First touchpoint | Free discovery call, then paid | Free scoping call, tool is free either way |
| Deliverable | Recurring workflow in a vendor tenant | A cron_jobs row on your Mac |
| How the process is described | A graph in a vendor UI | Plain English in the prompt column |
| Reaching apps with no API | Custom middleware, billable | Accessibility tree, built in |
| Per-run cost | Hidden in a flat retainer | cost_usd logged per fire |
| Cost to start | $5k to $40k plus retainer | Free, open source |
| Survives a subscription lapse | No, dies with the tenant | Yes, local SQLite row |
| Cross-team change management | Yes, real value here | No, book the human for this |
Orthogonal comparison. If your problem is negotiation, compliance sign-off, or process redesign, hire a human. If your problem is running a recurring task across a few apps, own the routine.
Not sure if your process is a routine or a real project?
Book a free 30-minute scoping call. We will run your process against the three measurements and tell you honestly whether Fazm covers it or you need a human consultant.
Questions people ask before booking
Frequently asked questions
Where do I actually book a call with a business process automation consultant?
Most consultancies that rank for this term put a free discovery call behind their 'book a call' button. Quantzig, K3 Techs, Wakeflow, BoostedCRM, and Grantbot all do this. The call is free; what follows is not. The standard funnel is discovery call, then a scoped proposal, then a paid build (commonly $5k to $40k), then a monthly retainer for maintenance. Fazm offers a free 30-minute scoping call too, at cal.com/team/mediar/fazm, but Fazm is a macOS tool you run yourself, free and open source, not an hourly engagement. Book the Fazm call if you want a second opinion on whether your process is something you can automate without hiring anyone.
What does the consultant's discovery call actually try to figure out?
Three things, in order. One: how many apps does the process touch, and do any of them lack a usable API. Two: how many people run it today, and how often. Three: does the output need to be signed, audited, or compliant. Those answers decide whether the engagement is a $5k point automation or a six-figure transformation. You can answer all three yourself in fifteen minutes, which is the point of this page.
What is the deliverable at the end of a consulting engagement?
Almost always a recurring automated routine: a workflow that fires on a schedule or a trigger and runs without a human. It might live in Zapier, Make, n8n, Power Automate, or a custom script in the consultant's environment. The asset runs in a tenant you usually do not control, and it stops when you stop paying. None of the pages ranking for this term show you the deliverable or what each run costs.
How does Fazm ship that same deliverable as something I own?
Fazm has a routines feature backed by a SQLite table called cron_jobs, created in database migration fazmV7 (Desktop/Sources/AppDatabase.swift). You describe the process in plain English, give it a schedule, and a headless runner at acp-bridge/cron-runner.mjs fires it on your Mac. The schedule column accepts three formats: cron:<expr> for calendar schedules like 0 9 * * 1-5, every:<sec> for intervals, and at:<iso8601> for one-shot runs. Every fire is logged to a cron_runs table with a status and a cost_usd value, so you can see exactly what each automated run costs.
Can Fazm reach apps that have no API, the way a consultant's custom build does?
Yes, and this is the part most consultant stacks cannot do cheaply. Fazm drives your real macOS apps and browser through the accessibility tree, not screenshots, using the same primitive VoiceOver uses to read the screen. That means it can operate eBay's seller hub, a UPS claim form, a Mercury wire review, a Google Doc, or a Stripe checkout even when there is no clean REST endpoint. A Zapier or Make automation breaks the moment a vendor deprecates the API version it depends on; an accessibility-driven routine keeps working because it targets the button labeled 'Save', not a pixel or an endpoint.
What does each automated run cost me, compared to a retainer?
Fazm records cost_usd per run in the cron_runs table, so a routine that fires every weekday morning has a visible, itemized cost you can read off your own machine. You bring your own Claude Pro or Max account, so model usage hits a plan you already pay for. A consultant retainer is a flat monthly fee whether the automation ran once or a thousand times, and you rarely see the underlying compute cost. Owning the cost line is the difference between renting an outcome and running it.
When should I still hire a human consultant instead of running Fazm?
Four cases. One: cross-team change management, where forty people across three departments disagree on how the process should run, and you need a human to broker buy-in. Two: compliance-signed workflows for SOX, HIPAA, or SOC 2 that require a named owner and a signed artifact. Three: a systems-of-record integration with custom SAML auth and no public surface that needs middleware specified. Four: process redesign, deciding whether the process should exist at all. Fazm automates a process you can describe; it does not negotiate or redesign one.
Is Fazm a consultancy or a product?
A product. It is a native macOS app (14.0 and up), free to start, and fully open source at github.com/m13v/fazm. The 'book a call' option exists so you can sanity-check fit before you commit time, not so we can scope a paid build. If your process is one Mac, a handful of apps, and no audit requirement, you will likely leave the call with a routine you can set up yourself rather than a proposal.
What happens to my automation if I stop paying?
With a consultant build inside their tenant, the automation usually dies with the subscription. With Fazm, the routine definition is a row in a local SQLite database on your Mac and the app is open source, so nothing is gated behind a vendor account you do not own. You keep the app, the routines, and the logs.
Adjacent guides
Keep reading
Small business automation consultant
What 17 prebuilt skills inside Fazm replace, and the narrow slice of work where a human consultant still earns the rate.
Business process automation meaning
What BPA actually means, stripped of the jargon, with a Mac-native example.
Business process automation tool
How a desktop agent compares to the Zapier, Make, and n8n stacks consultants assemble.
Comments (••)
Leave a comment to see what others are saying.Public and anonymous. No signup.