What actually happens in a 15-minute operational triage call.

If you've been in business long enough to have a broken system, you've probably also been through at least one "free consultation" that turned out to be a 45-minute sales pitch followed by a relentless drip campaign, a PDF brochure that somehow cost you a contact form submission, and a quote that materialised three weeks later with no reference to anything you actually said.

This isn't that.

The 15-minute operational triage exists for one reason: to give both sides an honest answer on whether Orchestrix is the right fit before anyone spends money or time on anything. It costs nothing. It takes 15 minutes. And roughly half the time, the honest answer is "no", which, if you think about it, is exactly what makes the ones that are a "yes" worth something.

Here's what it actually looks like.

The short version

Before the minute-by-minute breakdown, here's the summary:

• Free. No card details. No strings.
• 15 minutes maximum. If it starts running long, Alex stops the clock.
• A conversation, not a pitch. There's no deck, no screen share, no slide about "our methodology."
• You describe the bottleneck. Alex asks questions. You get an honest assessment of whether Orchestrix is a fit.
• Roughly half the time the answer is "no, and here's a more useful direction."
• If it's a yes, the next step is a workflow audit, a paid, fixed-fee engagement where the real mapping happens. The triage doesn't replace the audit; it qualifies whether the audit is worth doing.

What to bring

You don't need to prepare a presentation. You don't need to have the problem fully figured out. But it helps to have four things ready:

1. The one workflow that's driving you mad. Not the full list of everything that's broken, just the single thing that, if it were fixed, would make the biggest difference right now.
2. A rough sense of scale. How many people use this process? How often does it run? This isn't for pricing. It's for understanding whether the problem is a 50-line Python script or a full application.
3. The tools you currently use. What software is involved in the broken workflow? Even if it's just "Excel and a lot of copy-pasting," that's useful.
4. Your rough budget ceiling. Not a precise number, just a range. "Somewhere between £2k and £10k if the fix is solid" is enough. This matters because custom software starts from £1,000, automation from £2,000, and websites from £2,500. If the ceiling is £500, it's better to know that upfront.

Minutes 0–3: the context

The first three minutes are yours. You introduce the business: what you do, roughly how many people, who the customers are.

Alex is listening for one thing: what does normal operation look like here? Not the broken bit, the whole picture. A 12-person surveying practice operates very differently from a 30-person e-commerce brand, and the shape of the problem is different even if the surface symptoms look the same.

There are no wrong answers here. "We're a small accounting firm and our onboarding process is a disaster" is enough to work with.

Minutes 3–8: the problem

This is the core of the conversation. You describe what's actually broken: the manual process, the bottleneck, the thing that steals hours every week without producing anything that couldn't be automated.

Alex will ask three or four questions. They tend to follow the same pattern:

• "Who currently does this?" (Is it one person? The whole team? A contractor?)
• "How often?" (Daily, weekly, per client?)
• "What happens when it goes wrong?" (Does someone notice immediately, or does it surface three weeks later in a report?)

These aren't filler questions. The answers change the shape of the solution. A daily task that takes 20 minutes is a different problem from a monthly task that takes two days, even if both feel equally painful.

Minutes 8–12: the honest verdict

This is the bit that most "free consultations" skip entirely.

After hearing the context and the problem, the triage gives one of four answers:

"Yes, this is exactly what Orchestrix does." The problem is clear, the scope is reasonable, and there's a recognisable fix: probably an automation, a custom tool, or a workflow that an audit could map and a build could replace. If this is the answer, you'll hear a rough shape of what the solution might look like and what the audit process involves.

"Yes, but it needs a workflow audit first to scope it properly." The problem is real, but there are too many unknowns to give you a useful direction without seeing how the team actually works. An audit is the right next step, not because it pads the engagement, but because scoping a build without one is how you build the wrong thing.

"Not quite right for Orchestrix, but here's a more specific direction." The problem doesn't match what Orchestrix builds. Maybe it's a pure off-the-shelf SaaS fit, maybe it's a different specialism, maybe the scale isn't there yet. You leave with a more useful direction than you arrived with.

"Honestly, you don't need a consultant for this." Sometimes the best outcome is a five-minute explanation of a free tool, a better-structured spreadsheet, or a built-in feature of software you already own. If that's the answer, that's the answer. Orchestrix doesn't exist to generate billable hours out of problems that don't warrant them.

Minutes 12–15: next steps

If it's a fit, there are two paths:

1. Book a workflow audit on the spot. Fixed fee from £2,500. Written proposal within a week. Alex sits with your team, maps how the work actually happens, and produces a prioritised punch list with fixed-cost proposals for each fixable item.
2. Agree to think about it. There's no follow-up sequence. No "just checking in" email three days later. If you want to proceed, you book. If you don't, that's fine too.

If it's not a fit, the call ends with a direction: a specific recommendation, a different type of provider to look for, or occasionally a "come back when X has changed." Not a brush-off. A useful steer.

Things the bureau will not do during or after the call

This is worth being explicit about, because some of these are industry standard practice and Orchestrix just doesn't do them.

• No free strategy document. The triage is a conversation, not a deliverable. If you want a written output, that's what the workflow audit is for.
• No follow-up drip campaign. One follow-up email if there was a genuine "let me think about it." That's it.
• No pricing until after an audit. The triage might give you a rough range ("this is probably a £3k–£6k build"), but fixed-fee proposals come from the audit, not the call. Quoting before mapping the workflow is how budgets blow up later.
• No commitment to "think about it and get back to you." If the answer requires research, Alex will say so and give a timeframe. Vague "I'll look into it" responses don't help anyone.

Who the triage is genuinely useful for

The 15-minute triage is designed for a fairly specific type of business. It works well if you're a small UK business (somewhere between 5 and 50 people, £1m to £10m revenue), and you're running into at least one of these situations:

• Someone on the team is burning 15+ hours a week on manual work that shouldn't exist
• A critical process runs on a spreadsheet that's become fragile or untrustworthy
• You've tried buying SaaS tools and none of them fit properly
• You know something's broken operationally but can't pinpoint exactly what
• You've been burned by a consultant before and want deliverables, not advice

If any of those sound like your business, the triage is worth 15 minutes of your time.

Who should skip it

Not every enquiry is a fit, and it's more useful to say that clearly than to take the call and waste everyone's time.

Skip the triage if:

• You want a templated SaaS configuration. If you've already bought Monday.com or HubSpot and just want someone to set it up, that's not what Orchestrix does. Business automation here means custom-built solutions, not off-the-shelf configuration.
• You want to hire by the hour. Every Orchestrix engagement is fixed-fee. If you need a developer on an hourly retainer, that's a different model.
• You want a strategy-phase engagement. If the output you need is a 40-slide digital transformation roadmap, you're looking for a different kind of consultancy. The first deliverable from Orchestrix is a systems map and a punch list, not a deck.

Why this exists

The triage exists because roughly half the time, the best outcome for the client is an honest "this isn't us." If that costs Orchestrix a few potential conversions, that's fine. The other half are worth it.

A 15-minute call that ends in "here's who you should actually talk to" is more valuable to you than an hour-long pitch that ends in a proposal for something that's 70% right. The whole model here (fixed fees, audit-first, no strategy theatre) is built on the idea that a consultant who tells you not to hire them is more trustworthy than one who always finds a way to say yes.

If you've got a broken workflow, a spreadsheet that's running the business and shouldn't be, or a manual process that's costing someone hours a week, start a triage. You'll get an honest answer in 15 minutes. No deck. No pitch. No drip campaign.