# Ignium Consulting — Full Site Content

> Brandon Brown helps founders and operators build systems that run without them. Business coaching and operational advisory in New Orleans.

This file concatenates the substantive content of https://igniumconsulting.io as markdown for LLM ingestion. Last generated at request time.

## About

Ignium Consulting is the practice of Brandon Brown, a business coach and consultant based in New Orleans, Louisiana. Engagements focus on identifying the real constraint in a business (usually the founder), opening the books for honest financial clarity, building scalable systems and SOPs, deploying AI-powered operations, and designing the founder out of day-to-day delivery.

Clients include marketing and PR agencies, energy services firms, real estate developers, legal operations teams, nonprofits, accounting and CAS firms, SaaS and tech startups, and mediation and professional services. Engagements run 90 days minimum with biweekly one-hour sessions plus between-session access. Virtual coaching nationwide; in-person sessions in New Orleans.

## Approach

- **Constraint Identification** — Find THE bottleneck in the business (usually the founder) and design around it. Theory of constraints applied to real operations.
- **Financial Clarity** — Open QuickBooks in-session. P&L analysis, job costing, real margins. Decisions from numbers, not feelings.
- **Scalable Systems** — 30/60/90 onboarding plans, escalation maps, SOPs. Every "fire" becomes a repeatable process so the business runs without the founder.
- **AI-Powered Operations** — Boring automation that saves real money. Build and deploy the tools, not just recommend them.
- **Strategic Delegation** — Design the founder out of delivery. Hire, train, and hand off until the operator becomes a CEO.
- **Sales Discipline** — Tighten the pipeline, close rate by source, and the conversations that decide deals.

## FAQs

### What kind of businesses do you coach?
Marketing & PR agencies, energy services, real estate development, legal operations, nonprofits, accounting and CAS firms, SaaS and tech startups, and mediation and professional services. The industries change. The pattern doesn't.

### How does coaching work?
Biweekly one-hour sessions with between-session access for real-time support when things break. The initial engagement is 90 days so we have enough runway to identify the constraint, build the system, and prove the change.

### What makes your coaching different?
I open your QuickBooks in our sessions. I build and deploy the AI tools I recommend. I design your replacement — every engagement works toward making you unnecessary in the day-to-day. And I stay in the ring with you between calls.

### Do you coach remotely?
Yes — virtual coaching nationwide, plus in-person sessions in New Orleans.

## Contact

- Email: brandon@igniumconsulting.io
- Phone: +1-504-360-6898
- Location: New Orleans, Louisiana
- Book a call: https://calendly.com/ignium_consulting/intro

## Blog Posts

### How Do You Stop a Six-Hour Job From Turning Into 22?
Published: 2026-10-07 · 4 min read · Tags: scope creep, budget tracking, agency operations
URL: https://igniumconsulting.io/blog/budget-overruns-agency-work

> Work runs over budget when nobody owns the number. Name one person to watch hours every morning, set an alert at 80% of budget, and require approval before anyone goes over. Expect 60 to 90 days of repeating it before the team treats it as normal.

Two email campaigns came back at 22 hours against a six-hour budget, and nobody said a word until the numbers stopped adding up. An agency owner told me that on our call Tuesday morning. She had the data the whole time. A report every morning landed in her inbox with every task and every hour logged. Nobody acted on it.

Nobody owned the report, so it read like wallpaper. Most owners I talk to have a version of this.

## Why does work run over budget when everyone can see the hours?

Seeing a number and owning a number are two different jobs. Her report listed hours for the whole design team, 40 or 50 lines a day, and it flagged nothing. She scans it at 7 a.m., sees a wall of text, and moves on to whatever client fire started overnight.

The designer on those campaigns didn't understand the four-hour goal the system attached to new tasks. The software assigned that number on its own. She never asked what it meant, and nobody asked her. By the time 22 hours had piled up, everyone had a theory. Unclear expectations, too much polish on small details, a handoff that stalled. The owner couldn't say which one it was, and I gave her credit for admitting that.

## Who should watch the budget?

One person, by name. In this agency it's the project manager, and her job is simple to describe. She spends the first 30 to 45 minutes of every workday on the hours report, unless a client emergency pulls her away. She finds the jobs closest to their limit, writes a short morning plan, and sends it to the owner. The owner approves it or changes it.

I pushed for the morning plan because it forces a decision every day. You can ignore a report. You can't ignore a plan sitting in your inbox waiting for a yes.

The owner will meet with her every day for the first 30 days, and move to a lighter schedule. Before any of that starts, I'm going to talk to the project manager myself. She watched these hours pile up and didn't raise a hand, and I want to know whether she saw the problem and stayed quiet, or never thought the call was hers to make. If she doesn't want the job, better to learn that in week one than week six.

## What should the alert rules look like?

Three rules cover most of it, and each one fits in a Slack message. Warn at 80% of budget. Escalate before the work crosses 100%, not after. Require the owner's written approval for anything that goes over.

On a six-hour job, the warning fires at 4.8 hours. That's about the point where the designer knows whether the work will finish in the time left. Someone can ask a question while the answer costs little, and the owner can decide to spend more hours on purpose instead of finding out on the invoice. A designer who hears about the overage at hour five can say the brief was vague or the client sent three rounds of changes. A designer who hears about it at hour 22 has nothing to offer but an apology.

The agency had a second problem sitting under the first one. The owner covers every gap herself, which is how she ended up at her laptop at 10 p.m. most nights. A budget rule with no one to enforce it gives her one more thing to check after dinner. She has six or seven strong applicants for an open social media role, and I told her to make the hire so the process has more than one pair of hands.

## How long until the team follows the rules?

Longer than she wants. I told her to plan on 60 to 90 days of repeating the same explanation, in meetings, in Slack, and in one-on-one check-ins. Most teams hear a new rule once, nod, and go back to what they did last month. Nobody is being difficult. A habit that took two years to form doesn't swap out after one meeting. The ones that change are the ones where the owner says it again on day 40 as if it were the first time.

She needs to treat the overruns as information. If the designer gets scolded for a 22-hour job, the next overrun stays hidden until it's 30. If she gets asked what happened, the next one gets flagged at hour five.

To find the cause, the owner will have her operations lead sit with the designer for a few days and watch where the hours go. Nobody has to guess between perfectionism and a stalled handoff if someone can see it happen.

The first thing the owner is going to ask the designer is what she thought the four-hour number on that task meant.

This is the kind of work I do inside [Scalable Systems](/#approach) — naming an owner for every number, building rules that fire before the damage, and designing the founder out of the after-dinner checks.

### You Can Name the Month Your Revenue Drops. Most Owners Find Out When It Lands.
Published: 2026-09-15 · 4 min read · Tags: revenue forecasting, client retention, pricing
URL: https://igniumconsulting.io/blog/know-which-revenue-is-ending

> A revenue floor is the monthly number your business doesn't fall below, and defending it starts with knowing which accounts are ending before the month they end. Subtract the work that's wrapping, name the gap, and sell against that number instead of a vague sense that things are fine.

An agency owner I coach opened our call yesterday with two numbers. September lands around $51,000. October comes in near $47,000.

She wasn't guessing. Two engagements are wrapping — one ends outright, one changes shape — and she ran the subtraction before October started. That four-thousand-dollar gap was the most useful thing she said all hour.

Most owners I talk to can tell me what last month did. Almost none can tell me what next month does, and fewer can name the account that explains the difference.

## What does a revenue floor mean?

Hers is $50,000. Not a target — a floor. The number the business stays above every month before she lets herself think about the next $10,000 increment.

The distinction matters because a target gets chased when there's time and a floor gets defended on a calendar. She's under hers in October. That's a problem with a date attached, and a problem with a date is the only kind you can work on this week.

Without the floor, October is just a slower month. Slower months get explained after the fact — summer, the holidays, a client who went quiet. With the floor, October is a $3,000 hole she has to fill by selling something specific to someone specific.

## How far out can you see your revenue?

Take your recurring accounts and write next to each one the month the current agreement runs out. Not the month you think they'll renew. The month the paper says the work stops.

Most owners have never done this in one sitting. They know each account's status in isolation, which means they feel fine until three of them land in the same quarter. Then it looks like a sudden slump, and it wasn't sudden.

Her list had two accounts scheduled to change and one more at risk that wasn't on anybody's list — a client where her social work overlaps with what the client's publicist does, which means somebody there is going to ask why they pay for both. That account isn't ending. It's just the one where the question gets asked first.

She's going to the decision maker before the question comes up, to draw a line between what she executes and what the publicist handles. That's a different conversation than the one you have after the cancellation email.

## What replaces the revenue you're about to lose?

She's pricing new engagements at $2,500 to $3,500 a month. At that range, the October hole is one new client. That's the whole plan, and it's a plan because the number is small enough to name.

The trap is treating the gap as a growth problem. Replacement work carries a deadline that growth work never does. She needs the signature in September for the revenue to count in October, which means the prospects who have been sitting in her pipeline since July get a decision this week or come off the list.

She has one contract pending signature and a $2,800 one-time project that closed last month. The one-time project feels like progress and it isn't — it doesn't repeat. Against a monthly floor, only recurring work counts.

## Does new revenue have to come from new clients?

No, and this is where most service owners leave money sitting.

One of her accounts is a hotel paying $1,200 a month for content. They don't get community management — nobody's answering comments or handling messages. Adding that piece takes the account to about $1,500.

That's $300 a month from a client who already trusts her, already has the work in her production schedule, and requires zero pitching from cold. She has three or four accounts in that same shape: photography that hasn't been refreshed in a year, a medical practice with images from a different era of the brand, engagement work nobody's doing.

Four expansions at $300 covers the October gap without a single new logo. She'll still chase new business — she should — but the expansions close faster because the relationship is already there.

## What does a $250 prospect cost you?

One prospect this month wanted to spend $250 a month. Her packages start around $2,200.

She took the call, built a scope, and went back and forth before it fell apart. Three or four hours gone on a conversation that was over before it started.

That's the part people miss about a pricing floor. It's not about protecting margin on the deals you close. It's about the hours you don't spend on deals you were never going to close. A prospect nine times under your entry price isn't a negotiation, and treating it like one costs you the same afternoon you could have spent expanding the hotel account.

Her filter now runs before the discovery call, not during it. Budget range in the first email. If it's under $2,200, she sends the name of somebody who works at that level and moves on.

She's going to New York next month for a small business expo. Two days of programming. She's staying five, and she's spending the extra three booking meetings with the kind of accounts that pay $3,000 a month, because one of them has to start in October.

This is the kind of work I do inside [Financial Clarity](/#approach) — opening the books, naming the floor, and selling against a number instead of a feeling.

### Don't Test Your New Hire on Your Biggest Account
Published: 2026-09-01 · 4 min read · Tags: hiring, role design, team performance
URL: https://igniumconsulting.io/blog/test-new-hire-low-risk-account

> Most service owners hand a new specialist their biggest account because that's where the pressure is. Test the hire on a recurring, low-stakes client instead — one that repeats, where you already know what good work looks like, and where a weak month costs you a rework instead of the relationship.

An agency owner I coach decided this morning that her next hire is an email specialist. Her first instinct was to point that person at the account she signed three weeks ago — a national restaurant brand paying $4,900 a month, the biggest name on her roster.

That's the account she can least afford to get wrong.

The one she should hand over is a skincare client on a monthly email cycle. Same work every month. Campaign build, list segmentation, a send calendar that barely changes. Nobody is watching it but her.

## Why does the new person always get pointed at the newest account?

Because that's where the pressure is. You just signed something big, the work is stacking up, and the hire feels like the answer to that specific problem.

So you take the account with the most visibility and the least history and you put an unproven person on it. Most of the owners I talk to do this at least once.

The problem isn't the hire. It's that you built a test with no room to fail. If the person turns out to be average, you find out in front of the client who matters most, on work you can't redo without the client noticing.

## What makes an account a good test?

Three things. It repeats, you know what good looks like on it, and a bad month costs you a rework instead of a relationship.

The skincare client checks all three. She has run those emails herself long enough to know how many hours a clean build takes and where the work tends to go sideways. If a candidate turns in something soft, she catches it before it sends and fixes it in an afternoon.

The new restaurant account fails all three. It's four weeks old, the deliverables are still getting defined, and client access has been slow enough that her own team is waiting on assets. There's no baseline to grade against. If it goes badly she won't know whether the hire is weak or the account is chaos.

Run the test where you already know the answer. Then you're grading the person and not the situation.

## What do you do with someone who's good at half the job?

She has a designer who's been with her a while. Fast, responsive, answers on a Saturday. The design comes back needing enough rework that the owner has started rebuilding it herself.

The reflex is to decide whether to keep her. That's the wrong question this early. The better one is which accounts her real strengths fit.

Quick-turn work on established accounts plays to speed and responsiveness — a template that already exists, a swap of copy and images, a same-day request. New client work, where the visual direction gets built from nothing, doesn't.

So the designer gets narrowed instead of cut. No new design-heavy accounts, keep the fast-turnaround work, and the build-from-scratch design goes somewhere else. That's what the role should have been from the start. Most people who look like a performance problem are sitting in a job description nobody wrote on purpose.

## How do you know it's time for a specialist instead of another generalist?

When the same gap shows up in three unrelated places at once.

Hers showed up as the skincare client's monthly campaigns, a prospective e-commerce account that will need list segmentation and flows, and a grocery prospect who asked about email before the social work has even started. Three accounts wanting the same thing she can't produce at the quality she'd want to sell.

A generalist covers one of those and drowns on the other two. That's the signal.

The tell in the other direction is when the gap is one account. One account is a subcontractor or a stretch month. Three is a hire.

## What should the test account produce besides a hire decision?

A case study with numbers in it.

She sells email as an add-on right now, and it prices like an add-on because she can't point at what it did for anyone. Open rates don't sell. Revenue does — what the list produced, what conversion looked like before and after, how the flows got built.

The e-commerce work in her pipeline is the one that could carry that. Which is another argument for testing candidates on the recurring client first. By the time the e-commerce account lands, she'll know whether the person she hired can produce the kind of numbers she wants to put in a proposal.

## What does this look like this week?

She's tracking her own hours through the end of the month, which is how she'll find out what the email work costs her before she pays someone else to do it. The job posting goes up after that.

The first candidate gets one month of skincare emails. Same brief she'd give herself. She grades the build, the segmentation, and whether they asked about the list before touching it.

She leaves for New York next week, so the applications go out before Thursday.

This is the kind of work I do inside [Strategic Delegation](/#approach) — hiring, role design, and handoffs that don't break the business.

### Delegate the Checklist Before You Delegate the Role
Published: 2026-08-25 · 4 min read · Tags: delegation, operations, founder extraction
URL: https://igniumconsulting.io/blog/delegate-daily-operations-checklist

> Founders get stuck delegating because they try to hand off a whole role at once. Start with the checklist you run every morning. Train someone on it for an hour a day for a week, then have them send you one daily report of what looks wrong. The role can come later.

An agency owner I coach spent about an hour a day for a week walking a new hire through his morning routine. Not a job description. The actual list he runs before nine.

Team inbox. Support line. Active development projects. Client work sitting in Asana. Who's waiting on whom. She watches all of it now and sends him one short report a day with whatever looks off.

Five hours of training, spread across a week. That's what it took to get a founder out of the inbox.

## What should a founder hand off first?

The thing you do at the same time every day. Not the biggest task, not the one you hate most — the repeatable one.

Most of the owners I talk to try to hand off a role. They write a job description, hire someone, and then spend four months annoyed that the person keeps missing things. The role has judgment baked into it, and judgment doesn't transfer in an onboarding doc.

A checklist transfers. Open these five places, look for these specific conditions, tell me what you found. Someone can run that on day three and be useful.

The founder still owns the decisions. He just stopped being the one who scans for problems, which is where the hours were going.

## Why does the daily report matter more than the task list?

Because the report is what keeps you from losing visibility.

The fear underneath most stalled delegation is that work will slip and nobody will tell you until a client is upset. A daily flag report kills that. She's not asking permission — she's telling him what she saw. Two minutes to read, and he knows whether anything needs him.

He's still in the loop on everything that matters. He just isn't the one doing the looking, and the difference in his calendar is real.

There's a second thing that happens once someone else runs the checklist. You find out how much of the list was never necessary. Half of what he'd been checking every morning turned out to be nothing, and it only became obvious when a second person had to justify why it was on the list.

## What happens to the people whose work you just moved around?

This is the part founders skip, and it causes more damage than the handoff itself.

When the ops monitoring moved, his senior developer's scope shrank. She went from full-time to part-time hourly, focused on advanced development and special projects. That's a real conversation with a real person, and he had to have it before the new arrangement made sense.

His project lead picked up the website build. Before taking it on, he pulled his own timesheet and marked every line that could go to a junior or get automated. That's the move I want more owners to copy — before you accept new work, look at what you're already carrying and find what leaves.

Delegation moves down a level, not sideways. If the founder hands off but nobody else does, you've built a bottleneck one seat lower.

## How do you know the handoff worked?

You look at what the founder does with the time.

He used his first stretch of free hours to rebuild the monthly client reporting. Analytics data on leads, calls, completed projects, upcoming work — the whole report drafts itself in Gmail, and he reads it and hits send. About seven hours of setup for something that now runs close to fully automated, every month, for every client.

That's the return. Not that he feels less busy. That he had seven consecutive hours to build something the business will use every month from here on.

Owners who never get free never build anything like that. They stay at task level, and the business stays exactly as good as their personal attention span.

## What if the person doesn't pick it up?

Sometimes they don't, and you need to know that before month six.

I've got a client in energy services with a scheduler who wasn't scheduling. Two contracts signed on a Friday sat unscheduled the following week. Not a process gap — the process existed and had a checklist attached.

We set standards you can check without a conversation. Every signed contract gets a date on the calendar within 48 hours. Every status update lives in the CRM, not in someone's head. Thirty, sixty, ninety days, with the bar rising at each mark.

The owner works the scheduling board next to him for seven days, then steps out and watches whether it holds. Five-minute check-in each morning covering the schedule, open client communication, and hiring.

At day 30, you're not guessing. Either the contracts got scheduled inside 48 hours or they didn't, and you're having a different conversation.

## Where founders get stuck

The hour a day for a week feels like too much time. It isn't — it's the whole cost of the handoff, and it's cheaper than the four months you'll spend correcting someone you trained in a single sitting.

What actually stops people is that training week is boring and the payoff is invisible while you're in it. You're narrating your own habits out loud to someone who's taking notes, and it feels slower than doing the work.

Then week two arrives, the report shows up in your inbox at eight, and you read it in ninety seconds.

Next session with the agency owner, we're opening the first-half P&L together. He's never pulled it himself — his bookkeeper has always sent him the summary. Now he's got the morning back to read it.

This is the kind of work I do inside [Strategic Delegation](/#approach) — designing the founder out of day-to-day delivery.

### Your 44% Margin Is Hiding the Client That's Bleeding You
Published: 2026-08-20 · 4 min read · Tags: job costing, margins, pricing
URL: https://igniumconsulting.io/blog/average-margin-hides-worst-client

> A healthy average margin can hide one or two accounts losing money. Break margin out by client, strip personal expenses from your hard costs, and you'll usually find the problem is unlimited revisions on a fixed retainer rather than a price that's too low across the board.

An agency owner told me her average margin was 44% this week. That's a good number. Twenty minutes later we found a $1,100 monthly retainer that had burned through five rounds of edits on a single email, and a $2,500 account that had grown into $7,800 worth of work without anyone repricing it.

The 44% was real. It was also useless.

## Why does an average margin hide bad accounts?

Averages do what averages do. A book of ten clients where eight run at 55% and two run at 5% still averages out to something you'd be happy to report. The eight good ones are paying for the two bad ones, and nobody notices because the top line keeps growing.

Most owners I talk to look at the P&L monthly and the account-level costing never. That's backwards. The P&L tells you whether the business made money. The costing tells you which client made it and which one spent it.

She had the data. Her time was tracked, her contractor costs were logged, the retainers were all in one sheet. She'd just never sorted the column.

## What makes your margin number wrong before you even start?

Before you trust the percentage, look at what's sitting in your hard costs.

Her full mortgage was in there. Not a home-office allocation, the whole payment. So her margin was actually better than 44%, and every per-client cost was inflated by a fixed number that had nothing to do with any client.

That cuts both ways. Owners who run personal expenses through the business get a pessimistic margin and make bad pricing decisions off it. Owners who leave contractor costs out entirely get an optimistic one and make worse ones. She was about to bring on a part-time production coordinator at five to ten hours a week and hadn't yet pushed that cost into the accounts the coordinator would support.

Clean the inputs first. A margin built on a mortgage payment and a missing contractor isn't a number, it's a feeling. And there's an audit exposure sitting there too, which is its own conversation.

## Which account is actually draining you?

Sort by margin, lowest first, and read the bottom three.

Hers came back clear. One was a small retainer tied up in a trade arrangement, so the revenue never fully showed up as revenue. One was a $1,100 email package where a single deliverable was going five and six rounds deep. One was an account where nobody had ever defined who approves what, so work bounced between the client's team and hers until somebody got tired.

Look at what those three have in common. None of them was priced wrong at signing. All three had something on the delivery side that ran without a limit.

That's the pattern I see most. The low-margin client usually pays a fair price. They just consume more delivery than that price assumed, and no line in the agreement or the process says when it stops.

## Should you raise prices when margins slip?

Not first.

Her $2,500 monthly package was producing clean margins across most of the book. Raising it across the board would have punished eight clients for two clients' behavior, and it would have done nothing about the revision rounds, because more revenue doesn't stop the fourth round of edits from arriving.

So we left the price alone and put a cap on revisions. Two rounds. She'll watch the next cycle on the worst account and push back the moment it goes past two.

For the account with the approval mess, she's driving down there next Thursday for lunch to walk their team through who signs off on what. One conversation, in person, about workflow. If that fixes it, the margin fixes itself.

The general price increase is a blunt instrument. It's the right call when your whole book is thin. When two accounts are thin and the rest are fine, you have a delivery problem wearing a pricing costume.

## What about a client whose scope has quadrupled?

That one's different, and it's the one exception to leaving prices alone.

She had a boutique hotel prospect who'd started at the standard $2,500 monthly package. By the time the requirements came back, it was two to three reels a week, over a hundred pieces tied to their renovation, a specific AI editing tool they wanted her to use, and monthly on-site shoots in another city.

Scope creep is a few extra asks around the edges. This was a different product. She's rewriting the proposal at around $7,800.

Repricing an expanded scope before you sign costs you a conversation. Repricing it after you sign costs you the client or the margin, and usually both. The tell is when the deliverable list from the discovery call doesn't match the one in your head from the intro call.

She's also building tiers now, so the next hotel-sized request gets priced off a package instead of off a gut read at the end of a Zoom.

## What does this look like on a Tuesday?

Open your job costing. Add a column for margin by client. Sort ascending.

Pull anything personal out of hard costs and put in the real business-use portion. Add any contractor you've hired in the last ninety days to the accounts they actually touch. Rerun it.

Then read your bottom three and ask one question about each: is this priced wrong, or is delivery running without a limit? The answer changes what you do next, and most of the time it's the second one.

This is exactly the kind of work I do inside [Financial Clarity](/#approach) — opening the books so the numbers stop lying to you.

She's starting on September 1, tracking her own hours for a month so the next version of this has her time in it too.

### Why Your Cold Outreach Emails Aren't Landing
Published: 2026-08-04 · 4 min read · Tags: cold outreach, pipeline building, referral strategy
URL: https://igniumconsulting.io/blog/cold-outreach-needs-one-number

> Vague cold emails promising quality and value get ignored. Replace the pitch with one real performance number, a pricing comparison, and a specific ask tied to an actual event, and reply rates change fast.

An agency owner I coach who works with auto detailing shops lost two clients last week and watched two more pause work until September. That's four accounts gone or on ice, all at once, and no warning shot before it happened.

Her instinct was the right one: go wide. She pulled a list of roughly 250 shops from an industry directory and started emailing. Ten one day, ten the next, with calls to follow up starting Wednesday. The problem wasn't the volume. It was what the emails said.

## What's actually wrong with a mass cold-email push?

She showed me the draft. It talked about her team's experience, her commitment to quality, the value she could bring to a shop's marketing. None of that is false. None of it is memorable either.

A shop owner skimming email between customers doesn't retain "experienced" or "results-driven." Those words could describe any of the twenty agencies that pitched him this year. There's nothing in the email that only she could say.

## What makes a cold email actually get a reply?

One real number. Not a range, not an adjective, an actual figure that came from an actual client. She has a shop client whose lead volume jumped by a specific percentage after three months of work. Her ops lead has the exact figure. So the fix was simple: put that number in the first two lines, next to what the shop was paying and what a competitor typically charges for less.

That's the difference between "we drive results for auto shops" and "shop X went from 40 to 71 monthly leads in 90 days, and they're paying less than they were with their last agency." The second one gets read out loud to a business partner. The first one gets deleted.

## Why tie the outreach to a specific event instead of a general pitch?

She's heading to a trade conference in San Antonio the week of August 25. Instead of a generic "let's connect" email, the rewrite asks a single question: are you going to be in San Antonio? If yes, she offers fifteen minutes at the expo, no pitch, just a conversation. If no, the email still lands because it's specific enough to feel like it was written for that one shop owner, not blasted to 250.

Cold email conversion is almost always a specificity problem before it's a volume problem. Adding a real date, a real place, and a real number does more for reply rates than doubling the list size.

## Should outreach lean on strangers or on people who already trust you?

The other shift we made was where she's spending her energy. Cold email to a purchased list is the slowest way to fill a pipeline. The fastest way is asking people who already know her work to make an introduction.

She has active clients who like her. Most of the ones I talk to have never actually asked those clients for a warm intro to someone else in the industry. So the plan changed: before San Antonio, she's emailing and texting current clients directly, telling them she'll be at the conference, and asking if they know anyone else attending who's worth a coffee.

That's a different kind of outreach than the cold list. It converts faster because there's already trust attached to the ask. The cold emails still go out, but they're not the whole plan anymore, they're one channel among three.

## What does the plan actually look like now?

The original goal was fuzzy: generate leads at the conference. We tightened it to a number. She lost four clients, so the target is four replacement accounts plus a pipeline that doesn't depend on any single one of them showing up. That's a business goal, not a marketing goal, and it changes what counts as progress. A friendly conversation at a booth doesn't count. A signed contract or a scheduled follow-up call does.

She's also scheduling a separate conversation with her ops lead to figure out why those four accounts left in the first place. Fixing the intake pitch matters, but if the same pattern that lost four clients is still running underneath, a better cold email just refills a bucket with a hole in it.

## What happens next

The follow-up calls to the first twenty shops start Wednesday. She's sending the rewritten email, with the real number in it, to the next batch this week. And she's got three current clients lined up to ask for intros before she leaves for San Antonio on the 25th.

None of this is complicated. It's a spreadsheet, a phone, and one real number she almost left out of the pitch.

This is the kind of work I do inside [Sales Discipline](/#approach) — fewer pitches, sharper ones.

### Before You Post the Job, Write Down Every Task You Do
Published: 2026-07-28 · 4 min read · Tags: hiring, task delegation, operations
URL: https://igniumconsulting.io/blog/task-inventory-before-hiring

> Before hiring, list every task you do with weekly hours, how hard it is to train someone else on it, and what breaks if it's skipped. That list becomes your job requisition, not a vague sense that you need help.

A client of mine who runs a marketing agency showed up to our last call with a spreadsheet instead of a feeling. Most founders come to me wanting to hire because they're drowning. He came with a list.

Every task he does, scored four ways: hours per week it eats, how hard it would be to train someone else to do it, who currently owns it, and what happens if it doesn't get done. Forty-some rows. No guessing.

## What should actually go on a hiring wishlist?

Not "we need a project manager." That's a feeling, not a job description. The list is the job description.

We sorted his rows into three buckets: move this week, move within 30 days, and stuff only he can touch. The first two buckets are what you hire for. The third bucket is what you keep, on purpose, because someone has to.

Once he had that split, the job requisition wrote itself. Client onboarding, routine check-ins, first-line support, daily workload review, Slack responsiveness, project queuing. All recurring, all trainable, none of it requiring him specifically.

## Why do most founders hire for the wrong role first?

Because they hire for relief instead of math. His actual problem wasn't "I need more hands." It was that he was still the one validating every quarterly client report before it went to his strategists, still triaging support pings all day, still context-switching between fires that a $20-an-hour operator could put out.

None of that needed him. All of it needed someone who reports to him.

## How do you size the hire before you post it?

Pull real calendar data, not your best guess. I asked him to pull the last 60 days of his calendar, meetings and all, so we could see where his time actually went instead of where he assumed it went. Most founders overestimate the hard stuff and underestimate how much of their week gets eaten by things like reviewing the same report format for the fortieth time.

That data is what turns "I think I need help" into "here's 12 hours a week, here's what it's worth, here's who should own it." A candidate you can't cost-justify on paper is a candidate you'll resent by month three.

## What do you do with the estimates once you have them?

His first pass at the spreadsheet had soft numbers. A task listed as "a few hours a week" isn't hireable, because you can't price it and you can't hold anyone accountable to it. We went back through and tightened every row to an actual hours-per-week figure pulled from the calendar data, not a round number that felt right.

That tightening mattered more than the sorting did. Two tasks that looked similar on a gut-feel basis turned out to be six hours apart once he checked. The one that ate more time moved to the top of the requisition. The one that didn't got pushed to the 30-day bucket instead.

## What should stay out of the new hire's hands?

Reporting was the clearest example. His team's quarterly client reports were already mostly AI-generated drafts, with a strategist spending 15 to 30 minutes per report validating the recommendations before it went out. That validation step is real judgment and stays with the strategist. Producing the report itself doesn't, and can move to a lower-cost operator entirely.

Same logic on content. Clients care about two things: leads and completed projects. Technical detail like schema markup notes and internal opportunity lists was cluttering the client-facing report for no reason. That stuff still matters, it just belongs in the project management tool for the internal team, not in an email a client skims from their phone.

He also raised a question worth asking before you simplify anything: does anyone actually read these reports in full? Nobody on his team could say for sure whether clients opened the detailed version past the first page. Before you spend hours polishing a deliverable, it's worth finding out if the polish is landing on anyone.

## How long should you expect the handoff to take?

He's budgeting 90 to 120 days for the new hire to absorb the operational load, and he's staying on the hook for onboarding until that transition is done. Not indefinitely, not "whenever it feels ready." A number, on a calendar, that someone can be held to.

He also agreed to batch report reviews on set weekdays instead of touching them daily in scattered ten-minute blocks. Small change, but it turns a background hum of context-switching into two contained sessions a week.

The job posting is already live on Indeed and ZipRecruiter, with Upwork as a backup channel for the lower-cost report review work in the meantime. He's not waiting for the perfect candidate to fix the whole list at once. He's hiring for the twelve hours he can already prove.

### Why Your AI Tools Keep Making the Same Mistakes Twice
Published: 2026-07-25 · 4 min read · Tags: AI implementation, tool selection, operations
URL: https://igniumconsulting.io/blog/ai-project-context-rules

> If you're re-explaining your rules to an AI tool every time you open a new chat, the tool isn't the problem. Grouping related work into a shared project with one set of standing rules stops the repeat mistakes and cuts setup time to almost nothing.

A client of mine in energy services spent three separate chat sessions over two weeks asking an AI tool to build the same kind of dashboard three different ways. Each time, he started from a blank chat. Each time, he re-explained what the business does, what the data looks like, and what he wanted the output to be. Each time, the tool gave him something slightly off from what the last one gave him.

That's not an AI problem. That's a filing problem.

## Why does the same AI tool give inconsistent results?

Every new chat starts with zero memory of the last one. If you don't hand it the rules up front, it guesses. And it guesses differently depending on how you phrase the request that day, what mood you're in, how much context you bothered to paste in.

We fixed this on a call last week by building what I call a CTO project: one container that holds a single markdown file of engineering rules, and every chat related to that work lives inside it. New chat for the bonus calculator, new chat for the marketing dashboard, new chat for the sales dashboard — but all three inherit the same rules automatically. Naming conventions, deployment targets, tone, data formats, none of it gets re-typed.

## What actually goes in the rules file?

Not a philosophy. A checklist. My client's file has things like which repo each project lives in, what the API keys are called in code versus what they're called in the vendor's dashboard, and a note that revenue metrics should default to current-year numbers unless someone asks for lifetime totals. Small stuff. The stuff that's obvious to him and invisible to a tool starting from nothing.

Once that file exists, you're not writing documentation for documentation's sake. You're writing the thing that stops the tool from asking you the same clarifying question in every session.

## Does splitting work into different models actually help?

We also split his AI usage across three tiers instead of running everything on one model. The high-cost model handles review and architecture decisions — the stuff where a wrong call costs real time. A mid-tier model handles planning and breaking work into steps. The cheapest model executes the grunt work: writing boilerplate, running repetitive edits.

This isn't about chasing the newest model. It's about matching the cost of the tool to the cost of being wrong. Getting a dashboard's color scheme wrong costs nothing. Getting a deployment architecture wrong costs an afternoon. Treat those two tasks the same and you're either overpaying for simple work or underpowering the important calls.

## What slows this down in practice?

Access, almost always. Half our call wasn't about AI at all — it was Railway workspace permissions, a GitHub org he didn't have access to, and an API key that was named one thing in the vendor dashboard and another thing in the code. The AI tool wasn't the bottleneck. Getting the right humans access to the right repos was.

This is the part people skip when they get excited about a new AI workflow. You can have the cleanest rules file in the world, and it still won't deploy if nobody can see the GitHub org it's supposed to push to. We spent forty minutes just adding a collaborator so a build could see the repo it needed.

## How do you know the setup is actually working?

You stop re-explaining yourself. That's the whole test. If you're two months into using a tool and you're still typing out "remember, our fiscal year starts in April" at the top of every chat, the project structure isn't doing its job yet.

For my client, the marker was smaller than that. He asked for a dashboard to show total closed revenue, and without him specifying current year, the tool defaulted to current year because the rule was already sitting in the project file. That's the whole point. Not a bigger, smarter AI. Just one that doesn't need to be told the same thing three times before lunch.

By the end of the call, the bonus calculator had been moved into the shared project, the marketing dashboard prompt was drafted and waiting for him, and the Nimbus API key was sitting in the right field in Railway under the right variable name. None of it will make a roadmap slide. It just means his next chat starts already knowing what his last three chats had to explain from scratch.

### Your Commission Structure Isn't a Motivation Problem
Published: 2026-07-21 · 4 min read · Tags: sales compensation, commission structure, sales performance
URL: https://igniumconsulting.io/blog/sales-commission-structure-not-working

> A confusing commission plan won't fix a low-effort salesperson, and a great one won't save a broken product. Simplify the structure first, then evaluate the person against a clean number.

I sat in on a call last week where a client was ready to fire their salesperson over low effort. Fair complaint, probably true. But when we pulled up the actual commission plan, I understood why the guy wasn't hustling. Nobody would.

It was a sliding scale tied to revenue tiers, recalculated monthly, with enough moving parts that even the owner couldn't tell you what a $50,000 deal was worth without opening a spreadsheet. If your top salesperson can't do commission math in his head standing in a customer's driveway, the plan is broken before you ever get to the person.

This comes up constantly with clients running service businesses. The instinct when sales are soft is to blame the rep. Sometimes that's right. But most of the plans I look at would demotivate a great salesperson too, because they reward complexity instead of results.

## Why does a complicated commission plan kill performance?

A salesperson needs to know, in real time, what closing a deal is worth. Not eventually, not after the books close for the month. Now, mid-conversation, while they're deciding whether to push for the upsell or let a discount slide.

Sliding tiers break that. The rep hits $400k in a month and doesn't know if the next sale bumps him into a better tier or if that kicks in at $500k. So he stops thinking about the tier at all and just does the minimum. You built a system meant to reward top performance and it produces the opposite, because nobody can hold the math in their head while they're working.

The fix we landed on was blunt: flat commission rate, period. No tiers. Then layer milestone bonuses on top — hit $500k in trailing sales, get a bonus. Hit it again, get another one. Simple enough that the rep can calculate his own check before he leaves the driveway.

## Should you fix the plan before you fix the person?

Yes, and in that order. You can't fairly evaluate someone against a plan that confuses everyone, including you.

Once the new structure was on the table, the conversation shifted. It wasn't "is this guy motivated," it was "here's a flat rate, here's the bonus threshold, here's a 90-day landing period to ramp into it — now show me the numbers." That's a real evaluation. The old plan never gave anyone that.

We also talked about what a soft landing looks like for a new or transitioning salesperson. Ninety days to six months at a guaranteed base while they build pipeline, then a full transition to commission-only or a hybrid. Long enough that someone competent isn't punished for the ramp curve. Short enough that you find out fast if they're not going to make it.

## What's the actual bar for a salesperson to earn their spot?

For most of the service businesses I work with, one to two new clients a month is the number that keeps the business healthy. Not ten. Not a hockey-stick chart. One to two, consistently, is enough to sustain growth without overextending operations.

That's a useful bar because it's checkable. At the end of Q3, did the rep bring in enough new business to cover his own comp? If yes, keep going. If no, you've got a real decision — commission-only, restructure the role, or move on — and it's based on a number instead of a feeling.

The mistake is skipping straight to that decision without first asking whether the comp plan gave the person a fair shot. Constrain theory works here too: if the compensation structure is confusing, if role design forces someone to choose between hourly stability and commission risk with no clear tradeoff, that's the bottleneck. Fix the bottleneck before you fire the person standing next to it.

## What does a good plan actually look like on paper?

Flat rate on every closed deal. Milestone bonus at a clean revenue number, not a sliding scale. A defined ramp period with a guaranteed floor. And a single number — new clients per month, or revenue per quarter — that tells you whether the person is working out.

That's it. No twelve-tab spreadsheet. No monthly recalculation nobody trusts. A salesperson should be able to tell you what a deal is worth before they've finished shaking the customer's hand.

The client I mentioned is whiteboarding the new structure this week with the field team, aiming to have it live before the next quarter starts. The old spreadsheet gets deleted, not archived.

### You Grossed $1.2 Million Last Year and You Can't Tell Me If You Made Money
Published: 2026-07-20 · 4 min read · Tags: bookkeeping, profitability, cash flow
URL: https://igniumconsulting.io/blog/owner-who-cant-tell-if-theyre-profitable

> Most owners with messy books aren't lazy — they just never built a 30-minute weekly financial routine. Clean six months of transactions, reconcile one bank account, and run a simple cash-in cash-out spreadsheet. That's the starting line, not QuickBooks mastery.

I had lunch with a client last Friday who runs a seven-figure services company and couldn't answer one question: are you making money?

Not "how much." Not "what's your margin on residential versus commercial." The baseline question. Revenue minus costs. Positive or negative. He didn't know.

## How does a business that size lose track of its own numbers?

The same way it happens in pretty much every company I work with under $3 million. Nobody set it up right at the beginning, and then the business outgrew the mess faster than anyone cleaned it up.

His QuickBooks file has personal purchases mixed with business expenses. His partner's bank activity runs through the same account. There are credit card charges in there from two years ago that nobody categorized. The file technically exists, but it doesn't tell him anything true.

He's not dumb. He built a real company with real employees and real clients. He just never had the week where someone sat him down and said: here's the minimum you need to do, and here's how often.

## What does "clean books" actually mean for a small company?

It means you can pull up last month and trust what you see.

Not a perfect chart of accounts. Not accrual-basis GAAP compliance. Just: every transaction in the last 30 days is categorized, your bank statement matches QuickBooks, and you can look at a P&L without wondering if half the numbers are your partner's groceries.

We set a target: clean the last six months. Not the last three years — that's a project for the CPA and it'll cost real money. Six months gives you enough pattern to see where cash actually goes and which months hurt. It also gives your accountant something to work with when tax season comes around instead of a shoebox and a prayer.

The cleanup itself isn't complicated. Connect the bank feeds. Categorize transactions. Pull out anything personal and mark it as an owner draw. Reconcile one month at a time. Most owners I work with could get through a month in about two hours once they know what they're looking at.

## What's the minimum weekly routine to keep it clean?

Thirty minutes. That's it.

Fifteen minutes in QuickBooks reviewing and categorizing whatever came in that week. Fifteen minutes updating a cash-flow spreadsheet — what's in the account today, what's expected in, what's going out in the next two weeks.

The spreadsheet sounds basic because it is. It's not a forecasting model. It's a piece of paper that answers the question "can I make payroll on the 15th" without logging into the bank and doing math in your head at 11 p.m.

Most owners resist this because it feels like accounting homework. It's not. It's the same thing as checking the weather before you drive to a job site. You're not becoming a meteorologist. You're just looking out the window so you don't get caught in the rain.

## Why does mixing personal and business money get so expensive?

Because every personal charge that hits the business account costs you time twice — once to figure out what it is, and once to move it.

His partner runs personal purchases through the company card. Has for years. Every one of those charges has to be identified, pulled out, and reclassified as a draw against her LLC. That's not a five-minute fix when you're doing it across 18 months of statements. That's a weekend project per quarter, minimum, and if you're paying a bookkeeper $50 an hour to sort it out, you're spending real money on something that shouldn't have happened in the first place.

The rule is simple: separate cards, separate accounts, day one. If that ship has sailed, the next best day is today, and everything before today becomes the cleanup pile.

## What happens when billing is the actual bottleneck?

He's got a different problem on the revenue side. Billing is slow and manual, and the person who handles payments is also the person customers are waiting on for service. One person, one payment terminal, and a line of people who can't pay until that person is free.

That's a constraint theory problem. The bottleneck isn't effort — it's that the business designed a single point of failure into its cash collection process. The guy taking payments is the same guy running jobs. When he's in the field, nobody gets invoiced. When he's invoicing, nobody's in the field.

You fix it the same way you'd fix any constraint: either add a second terminal and a second person who can process payments, or move billing off of the field team entirely. Most companies this size can hand invoicing to a part-time admin or a VA for a few hundred dollars a month and free up their highest-paid field person to run jobs that actually generate revenue.

## When should you bring in a CPA versus doing it yourself?

When you've got entity structure questions you can't answer.

He's got an S-Corp, at least one LLC, and a partner with her own entity. That's not a QuickBooks tutorial problem. That's a "which entity does this expense belong to" problem, and the answer changes your tax liability.

But here's the thing — you still need to know what's in the file before the CPA touches it. Hiring an accountant to clean up a QuickBooks file you've never looked at is like hiring a mechanic to fix a car you can't describe. They'll do it, but it'll take longer and cost more than if you'd spent 30 minutes under the hood first.

He took a note to block 30 minutes next Monday morning. QuickBooks open on one screen, bank statement on the other, and the cash-flow spreadsheet in between. Not a big overhaul. Just the first week where he'll know his own numbers before someone has to ask.

### What Do You Do When One Lender Won't Let the Rest of the Deal Move?
Published: 2026-07-18 · 4 min read · Tags: capital structure, growth, real estate
URL: https://igniumconsulting.io/blog/one-holdout-lender-can-freeze-your-portfolio

> When a portfolio is financed across multiple loans and one lender won't settle, the whole structure can freeze at once. The fix usually means pulling a healthy asset into the deal to buy out the holdout — and it exposes how fast growth outruns the capital structure underneath it.

A client of mine sat in a hearing this month while a lender asked a judge to appoint a receiver over one of his properties. That's the lender saying, in court, that they don't trust him to run his own asset anymore.

He won. The judge didn't grant it. But winning a hearing isn't the same as winning the problem, and the problem is bigger than one lender.

## Why does one holdout lender freeze an entire portfolio?

Because the properties were financed separately, but the owner's credibility with every lender is shared.

He's got multiple loans across multiple properties, syndicated with different partners on different deals. One lender is playing hardball. The others are watching. One of them already signaled they're ready to settle if they see momentum — but nobody moves first in a standoff like this, because moving first looks like weakness to the next lender in line.

So the holdout isn't really a $2 million problem or whatever that one loan is worth. It's a referendum on whether every other lender in the stack believes this guy can still execute. That's what makes one stubborn party expensive out of proportion to their actual loan balance.

## Why do your strongest assets end up carrying your weakest ones?

Because that's usually the only lever left once a standoff drags on.

His plan, worked out with his partner, is to pull a large, healthy, fully-performing property into the refinancing pool. That asset throws off enough cash flow to bring the holdout closer to being paid in full and to recast two other loans at the same time. The property did nothing wrong. It's getting drafted into a fight because it's the only thing in the portfolio strong enough to move the needle.

This is the part that catches owners off guard when they're scaling with debt across multiple entities. You think you've built separation — different LLCs, different lenders, different deals, walled off from each other on paper. Then one piece goes sideways and you find out how connected everything actually was the moment you needed a rescue.

## What's the number, and why does saying it matter?

He landed on needing roughly seven million dollars to bring the loans current and recast the structure. Not a range. A number.

Owners sit in ambiguity longer than they need to because a specific number feels like a commitment they're not ready to make. But a vague sense of "we need more capital" doesn't move a bank CEO, a workout officer, or a recap contact. A specific number does. It's the difference between a conversation that goes somewhere and a conversation that's really just venting.

Once he had the number, the next move stopped being complicated. Call the CEO. Call the workout officer. Call the guy he knows who might do a recap. All three, same day, not spread across two weeks of hoping email gets a response.

## How do you keep operations running while you're fighting upstairs?

You don't get to stop running the business because the financing is on fire.

His team still does a morning check-in every day and updates a shared project board by end of day, regardless of what's happening with the lenders. Construction management continues. Client-facing product work continues — his team just landed a new hospitality client and got invited to pilot with another one. None of that is glamorous next to a courtroom fight over a receiver, but it's what keeps the business worth saving while the capital structure gets sorted out.

The founders I talk to who survive a stretch like this aren't the ones who found a clever financing trick. They're the ones who kept the operating rhythm boring and predictable while everything upstream was chaotic. The board gets updated. The check-in happens. Nobody's waiting on the owner to remember what's due today.

## What do you do with the person carrying too much of the business?

You don't wait until they burn out to make the call.

One of his key people is highly productive and sitting on work that's genuinely critical right now — the kind of person you don't want to lose mid-crisis. But she's overloaded, and he's weighing whether to keep piling on or start pricing out what it costs to lighten her load versus what it costs if she leaves in month four of a rescue.

That's not a hiring decision he can make cleanly with a spreadsheet, not right now. It's a judgment call about how much runway he has left in her before the answer gets made for him.

Meanwhile another team member is on his way out — finishing current work, giving up his equity, with a separation conversation already planned instead of a surprise one. That part, at least, isn't chaotic. It's the one clean transition in a quarter that's short on clean transitions.

He's got about eight to nine months of runway under current usage before this becomes a liquidation conversation instead of a refinancing conversation. The calls to the CEO and the workout officer are both going out this afternoon.

### How Do You Know If It's Your Salesperson or Your Commission Plan?
Published: 2026-07-16 · 4 min read · Tags: sales compensation, hiring, commission structure
URL: https://igniumconsulting.io/blog/salesperson-or-commission-plan

> When a salesperson underperforms, most owners assume they hired wrong. Check the commission plan first. If the rep can't calculate their payout on a deal while standing in the customer's driveway, the plan isn't driving behavior — and no amount of coaching will fix that.

A client in energy services told me this morning his salesperson isn't producing, and his first instinct was to pull back the production plan to match. Fewer crews, slower ramp, smaller year. Shrink the company to fit the person who isn't selling.

We killed that idea in about four minutes. The product is strong. The install teams are good. Demand is there — booking lead time sits at four to six weeks right now. None of that changed because one person stopped picking up the phone.

## Why do owners shrink the plan when sales goes soft?

Because it's the only lever that moves without a conversation.

Firing someone takes weeks. Rebuilding comp takes a Tuesday you don't have. But cutting the third crew from the plan? That happens in your head on the drive home, and nobody argues with you about it.

The problem is the two decisions run on different clocks. Adding a third production team pushes lead times to about eight weeks, which means you need sales capacity months before you need the crew. Shrink the plan today and you've solved a sales problem by capping the company. The salesperson keeps their job. You lose the year.

Keep the plan. Fix the comp.

## What's wrong with sliding commission tiers?

His current plan uses sliding revenue-based tiers. More revenue, higher percentage, stepped brackets.

Ask the rep what they'd make on the proposal sitting in their truck and watch what happens. They can't tell you. They'd have to know where they land in the bracket for the month, which depends on deals that haven't closed yet, which depends on things they can't see.

A plan that requires a spreadsheet to interpret doesn't change behavior in the field. It just gets reconciled at month end. The rep learns to treat commission as a surprise that arrives on the 15th instead of a number attached to the thing in front of them.

Complexity in a comp plan is a tax on effort. You're asking someone to do arithmetic before they get excited.

## What does a simpler plan look like?

Two shapes worked when we whiteboarded it.

The first: flat commission on every signed deal, same percentage from the first dollar, plus a milestone bonus at every $500k in signed revenue. The flat rate means the rep knows their number before they knock. The milestone gives them a reason to push a deal over the line in the last two weeks instead of parking it in next month's pipeline.

The second: quarterly commission tied to revenue or profit, paid on the whole quarter. Longer cycle, bigger check, better fit if your sales cycle runs past thirty days and you want the rep thinking about pipeline instead of this week's close.

Both beat brackets. Both fit on an index card.

If you go profit-based, be ready to open the books enough that the rep believes the number. A profit commission on financials nobody sees is a discretionary bonus wearing a costume.

## Should a new salesperson get a guaranteed period?

We landed on a soft landing of 90 days to six months — some floor while they build pipeline, then full commission.

The case for six months: a real rep needs a quarter to learn your product and a quarter to fill a funnel. Pay them like a beginner for two quarters and the good ones won't take the job.

The case for 90 days: every month of floor is a month you're paying for pipeline you can't inspect. Six months of guarantee against a four-to-six week install cycle means you'll know by month three whether this works, and you'll pay for three more months of knowing.

Most owners I talk to overpay for the ramp and underpay for the win. Shorten the floor. Raise the milestone. Let the person who's good get rich.

## Can you actually hire someone with high effort and high skill?

This is where he got stuck, and where most of them get stuck.

You want a rep who works hard and sells well. That person exists and they already have a job. The ones on the market usually bring one or the other, and you're picking which gap you'd rather train.

Effort you can't teach. Skill you can. Product knowledge, discovery structure, follow-up cadence — those are documentable, and if you've got templates and a tracker they transfer in a month or two. What you can't install in someone is the willingness to make the call they don't want to make.

That's also why the comp plan matters more than most owners think. A simple plan pays effort on a short delay. A bracket plan pays effort on a delay long enough that the person stops connecting the two.

The other trap is the hourly-versus-commission argument. Pay hourly and you get someone who's fine either way. Pay commission and you get someone who needs the deal. You already know which one you're building for.

## What if the operations side isn't ready?

Then don't hire the rep yet.

Sales capacity is worthless if the schedule can't absorb it. His constraint right now isn't leads — it's whether his ops lead can own the schedule without the founder in every conversation. Until that's true, a great salesperson just builds a backlog and a reputation problem.

So the sequence is: get ops running clean, get the ops lead to full capacity, then hire sales into the room you made. Not the other way around. Hiring a closer into a company that can't install is how you turn a sales problem into a refund problem.

The comp plan gets built now, though. Design it while you're not desperate. The plan you write when you need someone in the seat this month is always worse than the one you write on a Tuesday with a whiteboard and no candidate.

He's got Tuesday blocked. Two hours, no calls. The old tier chart comes down before the new one goes up.

### Your Deals Aren't Dying at the Pitch. They're Dying in the Follow-Up.
Published: 2026-07-12 · 4 min read · Tags: sales systems, follow-up, pipeline
URL: https://igniumconsulting.io/blog/sales-follow-up-cadence

> Most deals stall after the proposal goes out, not during the pitch. The fix is a steady automated follow-up cadence, a two-question opener that surfaces the real problem, and treating reminders as system prompts instead of personal nags. Retention and referrals beat cold outreach every time.

A client told me this week he'd stretched his follow-up from once a week to once every two weeks. His reason: he didn't want to feel like he was harassing people.

He's got three signed agreements sitting in his pipeline waiting on the other side to respond. And he just cut his own follow-up in half because it felt uncomfortable.

That's the whole problem in one move. The deals were close. Then the fear of being annoying did more damage than any prospect ever would.

## Why do deals die after the proposal goes out?

Because the person who wanted it got busy, and nobody reminded them.

Most of the deals I see stall don't stall on price or fit. They stall in the gap between the proposal and the signature, where the prospect meant to get to it and then a fire started at their own shop. Your quote is sitting in an inbox under forty other things.

The founder reads that silence as a no. Usually it's a not-right-now that turns into a no only because nobody kept it alive.

So the instinct to back off is backwards. You don't protect the deal by giving it space. You lose it.

## How often should you follow up without being annoying?

More than you think, and it should mostly come from a system, not you.

I told him to speed the cadence back up and let software carry it. When a reminder shows up as an automated prompt with the signed link right there, it reads as a process, not a person hovering. People don't feel harassed by a calendar. They feel harassed by a guy who sounds anxious.

That's the reframe. The problem was never the frequency. It was that every nudge felt personal, so he rationed them. Take himself out of the loop and he can follow up twice as often and feel half as pushy.

Text the link too. A signed agreement that lives in an email thread dies in an email thread. The same link in a text gets opened in the parking lot between jobs.

## What do you say when they've gone silent?

You stop pitching and ask two questions.

He was walking into shops and leading with the offer. I had him flip it. Open with something like how many cars do you want through here a week, then how many are you running now. Two questions, and the owner tells you the size of his own problem before you've said a word about what you sell.

Now you're not selling. You're standing in the gap between where they are and where they want to be, and everything you say next points at closing it. The pitch writes itself because they wrote it.

This works cold too. Most owners he meets have been burned by someone who overpromised. A diagnostic question lands different than a pitch because it assumes they know their own business better than you do. They do.

## Where's the fastest revenue actually hiding?

In the customers you already have.

We spent time on a conference coming up at the end of August, getting the attendee list, working out a scarcity angle where he only takes one shop per town so signing means locking a competitor out. All good. New logos are the slow, expensive game though.

The faster money is the people who already pay you. I told him to buy drinks for his current customers at the event and ask who they know. A happy customer will hand you an introduction that would take three months of cold outreach to earn. Retention and referral is the highest-return hour in sales, and it's the one most people skip because chasing new logos feels more like the job.

## The part that trips most people up

They treat follow-up like a personality trait instead of a system.

The founder who's good at it just built a machine that follows up whether or not he feels like it that morning, so the deal doesn't hang on his mood. The one who stretched his cadence to every two weeks was protecting himself from a feeling, and the feeling cost him deals he'd already half-closed.

He left our call with a short list. Speed the automated reminders back up, text the signed links, open every shop visit with the two-question line, and get the attendee roster before someone else does.

He's texting the three pending agreements today, links attached, no paragraph explaining himself. Just the link and a line asking if they've got any questions before they sign.

### The AI Rollout Nobody Warns You About Is a People Problem
Published: 2026-07-14 · 4 min read · Tags: AI adoption, change management, implementation
URL: https://igniumconsulting.io/blog/ai-rollout-change-management

> Most AI rollouts stall because companies treat them as software training instead of change management. The fix is redesigning workflows, mapping who benefits, and shipping fast prototypes that earn you the authority to lead. Adoption follows trust, not features.

A client called me this week in the middle of a six-week trial for a new AI tool inside his legal department. The CEO wants it. Adoption looks likely. And he's the one running the trainings, building the relationships, onboarding a new hire so he has time to manage the thing.

Here's what stood out. He wasn't worried about the software. He was worried about the two deputies who don't want it, the boss whose job he's doing without the title, and the fact that nobody has officially said who owns this.

That's the real work of an AI rollout. The tool is the easy part.

## Why do most AI tools get bought and then ignored?

Because someone treats the launch like a training session. Sit everyone down, show them the buttons, send a recording, call it done.

Then Monday comes and everyone goes back to the way they already work. The tool sits there. Six months later someone asks why nobody uses the thing they paid for.

The reason is simple. You didn't change how the work happens. You added a tool on top of a workflow and hoped people would rearrange their day around it. Most won't. They have deadlines and habits and no reason to trust that the new way is faster.

The ones who get adoption right redesign the workflow first. Where does the contract start, who touches it, where does it slow down. Then they put the tool at the exact point where it removes a step people already hate.

## Who has to want this for it to work?

Not everyone. And they don't all want the same thing.

My client mapped his three decision-makers before he built anything. The top lawyer cares about risk and keeping the peace. The operations side cares about speed. The litigation group is scared of being left out. Same tool, three different reasons to say yes.

So you don't sell one pitch. You build a version of the case for each person that speaks to what keeps them up at night. The risk person hears about fewer mistakes. The speed person hears about a 20% cut in contract cycle time. The left-out group hears they're first in line.

Most people running a rollout skip this. They send one email to the whole department and wonder why half the room is cold. You're not talking to a department. You're talking to five people with five sets of incentives, and you need most of them nodding before the group moves.

## How do you get put in charge when nobody named you the owner?

You don't wait for the title. You ship something.

My client's instinct was to push for a formal role first, get the org chart sorted, then start. I told him that's backwards. The authority follows the work, not the other way around.

Pick one small team. Build a quick prototype that solves one thing they complain about every week. Let it work in front of people. Now you've got proof. You already fixed something they watched break for months, and asking for room to do it again is a much easier conversation.

He's got a boss sitting on the AI steering committee who isn't doing much with the seat. So the plan is to ask for that seat directly and start bringing prototypes instead of slides. Same politics, different position. You stop being a name on a request and become the person the room already ties to progress.

## What breaks a rollout that looked like it was going fine?

Politics nobody put on the calendar.

The trial had CEO support and a real shot at full adoption. On paper, done deal. In the room, two deputy general counsels and my client's own manager were stepping on each other behind the scenes over who runs the change. That kind of friction doesn't show up in a status update. It shows up as a launch that keeps slipping for reasons nobody will say out loud.

The move there isn't to fight it head-on. Make the legal team the visible face of the rollout and use his manager's backing to smooth the parts he can't control directly. Give the credit away where it buys you cover. Keep the CEO sponsorship warm so when the friction gets loud, someone above it all still wants this to happen.

## The part most people get wrong

They think buying the tool was the decision. It was the easy 10%.

The other 90% is figuring out whose day changes, who feels threatened, who needs to look good, and how you get twelve people with different jobs to agree on a new way of working. No vendor demo covers that.

My client is spending his next month offloading his old tasks to a new hire so he can chase complaints across the department and turn each one into a quick win. Not a launch plan. A list of small, specific things that make one person's Tuesday easier, built one at a time until the tool stops feeling like something IT installed and starts feeling like how the place runs.

He's calling the top lawyer right after the vendor session ends to pin down what the man wants out of this. Everything else waits on that answer.

### Don't Open a Second Market Until You Can Explain Where Last Month's Leads Came From
Published: 2026-07-09 · 4 min read · Tags: growth, marketing metrics, expansion
URL: https://igniumconsulting.io/blog/when-to-expand-into-a-new-market

> Expanding into a new market copies your current system, gaps and all. Before you spend a dollar on a second location, you should be able to look at last month and say exactly where every lead came from. If your organic numbers are a question mark, fix the home market first.

A client of mine is about to launch in a second state, and on the same call she couldn't tell me why her website traffic dropped last month. Those two facts sat next to each other and neither of us liked it.

She runs a mediation practice. Home market is solid, the phone rings, and she wants to plant a flag in another state by the end of Q3. On paper it reads like a business ready to grow. Forty-one consult requests last month at about forty-nine dollars each. Google's Performance Max pulls them in around thirty-five a piece while plain search runs her ninety-one. She just moved ten grand into savings. That's a healthy picture.

Then the other side. Direct traffic to her site fell off since she brought on an SEO guy in the spring. Her analytics showed a traffic spike, but when we looked closer it was mostly junk referrals from overseas bots. The guy reports her keyword rankings climbing every month. Actual organic sessions in June: about eighteen. She pays him five hundred a month.

So the only numbers she fully trusts are the paid ones. Everything organic is a shrug. And the plan is to bolt a whole new state onto that.

## What actually breaks when you expand too early?

Expansion doesn't add a market. It copies the one you already run. Whatever system you have at home, you run it again somewhere you know less about, with contacts you haven't made yet and rules you haven't learned.

If a lead comes in from the new state, she won't know whether it was the ad, the ranking, or luck. That's the exact problem she has at home right now, except in the new market she'd be paying for ads and a site build while flying half-blind on where the results come from. You don't want to debug attribution in two places at once. You want to debug it once, at home, where the volume is high enough to see patterns.

The ones I talk to who expand well tend to be a little bored with their home market before they leave it. It runs without them watching. They can read it in their sleep. She's not there yet. She's still finding out what changed on her own site.

## Why do good rankings produce no traffic?

The SEO story is the tell. Rankings are a number a vendor can hand you that feels like progress. Clicks are the number that pays rent. Those are not the same thing, and eighteen sessions in June says so plainly.

Before she spends another five hundred, the vendor owes her one plan: how does position on a search page turn into a booked consult? If he can draw that line, keep paying. If he can't, she's renting a dashboard that goes up and to the right while the phone stays quiet.

I told her to install a changelog plugin this week so she can see exactly what changed on the site the day her direct traffic dropped. Half of these mysteries are a setting someone flipped and forgot. You can't fix what you can't date.

## So when are you actually ready to expand?

When you can pull up last month and say where each lead came from without guessing. That's the bar. Not a feeling that things are going well. A number you'd bet on.

She's closer than she thinks. The paid side is clean. She knows Performance Max beats search roughly two to one, she knows her cost per consult, she trusts those figures. If she gets the organic tracking honest, she'll have a market she can actually read, and then a second one makes sense.

The move isn't to freeze the whole plan. Keep the low-cost parts moving and hold the paid spend. Spend July researching the new state's divorce law and pricing. Take the August trip and meet people in person. Have her assistant start building a contact list. All of that is cheap and none of it commits her to ads before the home numbers are honest.

## How should you introduce yourself in a market that already has competitors?

One more thing we hit, because it matters more than the website. She's nervous about looking like a threat to mediators already working that state. Good instinct.

Don't walk in as a competitor. Walk in as a referral partner. Financial planners, family-law attorneys, chapter presidents of the groups her clients already belong to, these people send work to whoever they trust, and they'd rather hand off a case than turn it away. That's a warmer door than trying to out-rank someone who's been there ten years. And she doesn't need to announce that her own move to the state is still tentative. That's her business, not the opening line.

The plan we landed on is small. Research in July. Handshakes in August. Ads only once the home dashboard tells the truth. No new state until the current one stops being a mystery.

So the first real task this week isn't the launch. It's the changelog plugin and one direct question for the SEO guy: show me the eighteen.

### How Do You Know If Your Cold Outreach Is Actually Working?
Published: 2026-07-07 · 4 min read · Tags: outreach, pipeline, sales cadence
URL: https://igniumconsulting.io/blog/track-outreach-messages-replies-proposals

> Most founders can't tell if their cold outreach is working because they track effort, not steps. Count three numbers each week — messages sent, replies, and proposals — hold a baseline for a month, then raise volume once you know your conversion rate. That turns guessing into a dial you can turn.

An agency owner I coach sent nine cold messages last week and had no idea whether that was good. She got three replies, and five people opened her proposal. Strong? Weak? She couldn't say, because she'd never written the numbers down before.

That's the trap with outreach. You feel busy, and you have no read on whether the work pays off.

We fixed it with three numbers.

## Why does outreach feel like a black hole?

Because most people track effort and stop there. They send a batch of messages, hear crickets for a few days, and decide the channel is dead. Then they go quiet for two weeks and start over cold.

The batch itself is invisible. Nine messages one week, zero the next, four the week after. No pattern, so no way to learn. You can't improve a number you never wrote down.

She'd been doing outreach on Upwork this way for months. Good samples, decent writing, no record of what came back. So the first thing we did was stop and count.

## What three numbers should you actually track?

Messages sent. Replies. Proposals submitted. That's the whole system.

Messages is your input — how much you put in the top. Replies tell you if your opener lands. Proposals tell you how many conversations got real enough to quote. Each number checks a different part of the funnel, so when one drops you know where to look.

She set July as a baseline month at ten messages a week. Not a stretch goal, a floor. Ten every week, same day, tracked in one place. July doesn't need to close a single deal. You're finding out what ten messages produces, so August has a number to measure against.

## What if the messages aren't converting?

Then you fix the message before you send more. Volume on a bad opener just burns your week.

Her replies were landing around a third — three out of nine. That's a live opener, so the issue isn't the hook, it's what happens after. We tightened the proposals: shorter, with a relevant work sample right in the first message instead of a link she hoped they'd click. Show the thing. Don't make them go find it.

If replies had been one out of nine, we'd have rewritten the first line and left everything else alone. The numbers tell you which lever to pull.

## When do you scale volume?

After the baseline, not before. Once she knows ten messages a week yields three replies and a proposal, August becomes math. Want two proposals a week? Send twenty messages.

That's the part most founders skip. They either sit at low volume forever or blast a hundred messages with no idea what a hundred should return. A month of honest tracking turns the whole thing into a dial. You know the input, you know the output, and you turn it up when you want more.

## Should you write a note on LinkedIn connection requests?

Skip the note. Send the bare request, then land in their comments and DMs after they accept.

Reply rates on connection notes have fallen off a cliff. A cold pitch stapled to a request reads as a pitch and gets ignored. A plain request gets accepted, and now you're connected with room to start a real conversation. I post four or five times a week, and most of my inbound starts with a comment, not a cold message.

Build the list with Sales Navigator so you're targeting the right people and watching who's active. Someone posting every day is easier to reach than someone whose last login was March.

## What about the relationships you already have?

This is the part she almost walked past. She'd spent months chasing new markets while a stack of past clients and warm contacts sat untouched.

Before you spend a dollar earning a stranger's trust, go back through your old client list. The contact who moved firms. The account that paused last fall. The referral partner you meant to thank and never did. Those people already know your work. A short check-in reopens more doors than a week of cold messages.

She's got one former client she's re-engaging next month and a growth marketer who hands off the exact execution work she sells. Neither cost her anything to find. They were already in her phone.

## So what separates the founders who win at this?

They don't send the most messages. They send ten a week, every week, and they write down what comes back.

Her homework this week was ten proposals before she leaves town Tuesday. Same ten as last week. Same ten as next week. The difference now is she's writing down what each ten is worth.

### Why Do Things Break Every Time You Change Managers?
Published: 2026-07-06 · 4 min read · Tags: delegation, team performance, operations
URL: https://igniumconsulting.io/blog/work-breaks-after-leadership-turnover

> When leadership turns over fast, work breaks because no one owns the specific tasks a departing manager used to carry, not because the crew got worse. The fix is naming one owner per task and running a five-minute daily review of yesterday's misses. In energy services, that cut repeat field errors within weeks.

A client in energy services called me frustrated because two jobs got redone in a single day. A crew left a large attic opening uncovered, and another cut a batch of rigid insulation to the wrong size. His first read was that he needed better training or a new checklist app.

He didn't. He'd changed field leadership three times in four months, and nobody owned the parts of the job that kept breaking.

## Why does work break when you change managers?

When a manager leaves, the tasks they carried don't leave with them. They just stop having a name attached.

The audit still needs someone to check for drop soffits. Somebody still has to run the pre-blow checks before the crew touches the attic. Hours still need watching. When the person who handled all of that walks out, those tasks don't register on a report as missing. They surface three weeks later as a job that has to be redone.

Most owners misread that gap as a people problem. The crew got sloppy. The new hire isn't ready. So they buy a training program or a fancier software and wait for it to fix a hole that software can't see.

## What actually fixes it?

Name one owner for every recurring task, and write the name down.

We sat down and built a running list of everything the old lead used to do. Not a job description. An actual list of tasks, with a specific person's name next to each one. The new operations lead now owns field issues and watches crew hours. That's it. When a soffit gets missed now, there's a person who was supposed to catch it, not a vague sense that the system failed.

This sounds obvious. It isn't happening at most of the companies I talk to. Owners assume the work is covered because it used to be covered. Nobody re-checks the list after a manager leaves, so the tasks fall into the gap between the person who left and the person who hasn't been told it's theirs yet.

The list did something else too. It gave us a place to put the corrections. The audit template got a new line to check the kitchen and attic for drop soffits. Rigid insulation now gets cut to 14.5 by 24. Blower-door and thermal-camera checks happen before anyone blows attic insulation. Every one of those fixes has an owner. Without the owner, they're just notes nobody reads.

## Do you need a new system or a daily habit?

A habit. We put a short morning meeting on the calendar, same time every day.

Five to ten minutes. Review yesterday's misses, plan today's fixes. That's the whole agenda. The point isn't to add a meeting. It's to shrink the distance between a mistake and the person who owns it, from three weeks down to one morning.

When leadership keeps turning over, people stop trusting that anyone's watching. A daily check at a fixed time rebuilds that without a speech about accountability. The crew sees the misses get named out loud every morning, and the work tightens up on its own. Nobody wants to be the recurring line item.

The cadence matters more than the content. Same time, same room, every day. If it floats around the schedule, it dies in a week and you're back to finding out about the attic opening when the customer calls.

## How do you know it's working?

You watch the same mistake stop repeating, and you watch your numbers hold while you fix the mess.

Here's the part that surprised him. While the field was a wreck, sales were fine. His closer booked 172 projects that month and hit her goal. June lead volume came in a touch above the prior year. The business was closer to stable than it felt from inside the daily fires.

That's usually true. When leadership turns over, the noise makes an owner feel like the whole thing is falling apart. The financials say otherwise. Demand held up the whole time. The gap was four months of nobody owning the handoffs, and a founder reaching for a new tool instead of a name.

We also added a marketing-source tab to the sales dashboard, so lead data pulls straight from Google, TV, and referrals instead of getting retyped. Same principle as the field list. Give the number one clear source and one owner, and you stop arguing about whether to trust it.

## What to do this week

If you've swapped a manager in the last quarter, pull up everything that person used to handle and put a name next to each line. You'll find three or four tasks that belong to nobody. Those are the ones about to break.

Then set a five-minute morning review at a fixed time and run it tomorrow. Not next week. The whole thing works because it's boring and it repeats.

His audit template now has one line that didn't exist a month ago: check the kitchen and attic for drop soffits before you blow. That line is there because someone finally owns the audit.

### The Fastest Way to Write SOPs You'll Actually Use? Record Yourself Doing the Job.
Published: 2026-06-27 · 4 min read · Tags: SOPs, AI tools, operations
URL: https://igniumconsulting.io/blog/ai-sops-from-field-recordings

> The reason your processes never get documented is that the person who knows them is too busy running them. Record yourself doing the job on your phone, transcribe the audio, and let AI draft the SOP from the transcript. You edit instead of writing from a blank page.

A client in energy services is back out in the field running service calls himself because two people left, and none of what he knows is written down anywhere. When a job came back half-finished last week, a customer skipped the office and called his personal cell with an open-ended ask. There was no system to catch it because the system is him.

This is the spot most owners I talk to get stuck. The knowledge that runs the company lives in one or two heads, and the people who could write it down are the same people too busy using it to stop and type. So the SOPs stay theoretical, the new hires shadow whoever's free, and the owner stays the bottleneck.

## Why don't the SOPs in your head ever make it onto paper?

Because writing a process from a blank page is slow and boring, and you're good at the actual work, not the documenting.

His service tech left and took the routine with him. Now my client knows the right order to check a dehumidifier setup, what to tell the customer, what to flag for a callback. He's done it a thousand times. Ask him to sit down Friday afternoon and write it out and it never happens, because Friday afternoon has six other fires and a blank Google Doc loses every time.

The work isn't the problem. The translation from doing to documenting is the problem, and that's the part nobody has time for.

## What does it cost you when the process lives in one person?

You become the escalation path for everything, including the stuff that should never reach you.

The half-finished job is a clean example. The office didn't have a script for taking the message, so instead of routing it to the right ops manager, the customer ended up on the owner's cell. He's now doing the field work, the triage, and the cleanup, which means the business can't grow past what his calendar holds. Most owners file this under being busy. The calendar hides what it really is, which is one person the whole operation routes through.

The tax shows up when someone's out. One departure and suddenly there's no record of how anything runs, so the owner straps the tool belt back on. Call it a staffing gap if you want. Staffing was just covering for a documentation gap.

## How do you get the process out of your head without stopping to write it?

You talk instead of type. He's going to record himself on his phone while he runs the next few service calls.

Not a polished script. Just narrating what he's doing as he does it, the way he'd explain it to a new tech riding along. Check this first, here's why, here's what a bad reading looks like, here's what I tell the homeowner. Two or three minutes of real audio per task, captured while the work is already happening, so it costs him almost no extra time.

The trick is that talking through a job you know cold is easy. You can do it one-handed in a crawlspace. Writing the same thing at a desk feels like homework. So you move the capture to where the knowledge actually lives, which is in the middle of the job, out loud.

## Where does AI actually help here?

It does the part you hate. You feed the transcript in and it drafts the SOP.

The flow is short. Record the visit, run the audio through a transcription tool, paste the transcript into an AI assistant, and ask it to turn the ramble into a clean step-by-step procedure. What comes back isn't perfect, but it's a draft with the steps in order and the reasoning attached. He edits a draft instead of facing a blank page, and editing is ten times faster than writing.

A few of these and he's got the start of a real service playbook, built from how the work actually gets done rather than how someone imagined it should. The data quality is better too, because it came straight from the field instead of from memory three weeks later. Garbage in, garbage out cuts both ways, and a same-day transcript beats a Friday reconstruction every time.

## What has to change in the office for this to stick?

The documents are half the fix. The other half is making sure calls stop landing on the owner's phone.

We set a simple rule: the office takes a specific message, not an open-ended one. What's the address, what's the issue, what was the last service. Then it routes to the right ops manager instead of forwarding the whole mess upstream. The SOPs give the office something to route against, and the routing protocol keeps the owner out of the middle. One without the other doesn't hold.

He's bracing for a short-term hit while this gets built, and that's the right call. Pulling himself out of every loop slows things down for a few weeks before it speeds them up. The owners who skip that step stay the smartest person on every call forever.

He starts recording Monday. First task on the list is the dehumidifier walkthrough, the exact one that left with the tech who quit.

### You're the Only One Your Clients Trust. That's Why You Can't Get Off the Call.
Published: 2026-06-25 · 4 min read · Tags: Delegation, Founder Extraction, Client Management
URL: https://igniumconsulting.io/blog/hand-off-client-calls

> Founders get stuck on every client call because clients bought them and were never handed anyone else to trust. Getting off the calls takes a named owner, a 90-day runway, blocked prep time, role-play before live meetings, and a playbook built from recorded calls so someone can run the meeting the way you would.

An agency owner I coach sits on every client call her firm runs. She wants off them. She's been blaming her calendar for something her calendar can't fix.

This came up on a coaching call this week. She runs a PR shop, just added four clients at once, and her biggest account is about a third of her revenue with her as the only point of contact. She has good people. None of them lead the calls. So the team grows and her week doesn't, and every new client makes the trap tighter instead of looser.

## Why can't I get out of client calls?

Because the clients bought you. You hired help for the work behind the meeting and stayed the face in the meeting, so the client still thinks you are the service. Add a person to the back end and your calendar doesn't move. The constraint was never hours. It's that nobody else in the room carries the trust.

That's also why throwing a smart hire onto a live call goes badly. The client clocks that they got handed off, and the hire is learning the relationship in front of the person paying for it. You can't fix a trust gap by surprising someone with it.

## How do I hand off a client relationship?

Name one owner, give them ninety days, and make training that person somebody's actual job instead of a thing that happens between fires.

She put her operations lead in charge of it — owning the training and the scheduling, not running it as a favor on the side. The first move was blocking prep time on the calendar before each client call, so the handoff has a rehearsal built into it. A meeting someone walks into cold is a meeting they'll walk out of having lost ground.

Then you match the call to the person. One of her people spots the right priorities but follows through in fits and starts, so she isn't ready to lead the touchy accounts yet. She gets the low-risk calls to practice on. The big account doesn't go to a trainee on day one. You move people up as they earn it, not as the calendar demands it.

## How do I make someone run the call the way I would?

You build a playbook out of what you've already said. Two and a half years of how she handles a nervous client, a budget question, a missed deadline — all of it lives in old Slack threads and recorded calls. Pulled together, that's a guide a new person follows instead of guessing their way through.

The big account gets its own version. The person she's putting on it learns that client's specific history and quirks, not PR in general, because the value she brings to that call is the two years of context, not the job description. Hand over the context and the person can stand in for you. Skip it and they're improvising with your largest invoice on the line.

Role-play is where this gets real. Before anyone leads a live call, you run the hard parts as a drill — the price pushback, the unhappy founder, the scope creep that shows up at minute forty. The first time your hire hears the tough question shouldn't be with the client listening. Practice the call before the call, and the live one stops being a coin flip.

You also stay in the room while you train. The handoff isn't a cliff. For the first stretch the new lead runs the meeting and you sit in, quiet, and you debrief after instead of jumping in during. The client gets used to the new face while you're still there, and your hire gets reps with a net under them. A few weeks of that and you start skipping calls one at a time, watching for the ones that go fine without you. Those are the relationships that are actually handed off. The ones that wobble go back on your calendar for another round.

## What does getting off the calls actually buy me?

Room to fix the thing that scared you into staying. Her biggest account being a third of her revenue is the real risk, and she can't chase new business while she's the one running every existing meeting. Founder extraction and growth are the same project. The hours she pulls back from calls are the hours that go into the accounts that lower her concentration.

The work here is making yourself replaceable on purpose, one relationship at a time. Not all at once, and not by hoping someone steps up. By picking the order and training to it.

In two weeks she's sitting down with her ops lead, calendar open, assigning a call leader and a prep block to every client meeting for the next eight weeks — including the big one she's never let anyone else touch.

### How to Re-Engage Cold Leads Without It Feeling Like a Sales Call
Published: 2026-06-18 · 4 min read · Tags: Cold Leads, Follow-up Cadence, Sales Process
URL: https://igniumconsulting.io/blog/re-engage-cold-leads

> Most cold leads aren't dead, they're unsorted. The fastest way to revive an old lead list is to make the first calls research instead of a pitch: tell people you're not selling, ask what happened, and tag why each lead went cold. Sort first, sell second.

Most cold leads aren't dead. They're just unsorted.

I sat in on a coaching call this week with an energy-services contractor — home weatherization, crawl spaces, that kind of work — and the owner had a pile of old leads sitting in his CRM doing nothing. People who asked for a quote three, six, nine months ago and then went quiet. His instinct was the normal one: call them and try to close them.

We did the opposite. We turned the first round of calls into research instead of a pitch.

## Why do leads go cold?

Nobody knows, and that's the problem. A lead marked stale could mean five different things. They went with a competitor. The timing was off. The price was over budget. They're still deciding. Or they're sitting in the pipeline and somebody forgot to follow up.

Each of those needs a different response. Treat all of them like a hot prospect who's ready to buy and you'll burn the list and learn nothing.

So the first job is triage. We set up a handful of outcome tags in his CRM — competitor, timing, budget, undecided, still active — and made the point of each call to figure out which bucket the person belongs in. One or two fields logged per call. That's the whole ask.

## What do you say when you call someone who ghosted you?

You tell them you're not selling. That line does most of the work.

The opener we built sounds close to this: hey, you reached out a while back about your crawl space and we never got you a real answer — I'm not calling to sell you anything, I just want to know what happened. Then you stop talking.

Most people will tell you. They went with someone cheaper. They got busy. They're still thinking about it. Once they've told you where they landed, you've got an opening that doesn't feel forced. If they're on the fence, you offer a quick call with someone on the team to walk through next steps. If they already hired a competitor and they're happy, you thank them and ask who else might need the work.

That last move is the one most contractors skip. A happy customer who picked someone else is still worth a referral.

## Who should make these calls?

For this client, it's a new operations hire. He's splitting his week between shadowing crews in the morning and making calls in the afternoon, with the owner meeting him for an hour every Monday to plan the week.

We didn't hand him a script to read word for word. We gave him a checklist and a loose script — the opener, the five categories, the two questions to close — and told him to record the first calls. Then we run the recordings through transcription, pull out what worked, and tighten the script from real conversations instead of guessing at one in advance.

The recording part matters more than it sounds. After thirty calls you can hear which objections keep coming up and which responses fall flat. You can't design that on a whiteboard. You have to collect it.

## How do you know if it's working?

You don't measure the first batch by closes. You measure it by what you learn.

The first thirty calls are a learning period. The question isn't how many appointments did we book — it's where should this person spend his time and whether these leads are worth chasing at all. If twenty-five of the first thirty already hired someone else, that tells you the follow-up window is too late, and the real fix is upstream in how fast new leads get a call in the first place.

The owner wanted to log every detail of every call. We talked him out of it. One or two items per call, max. The second you make calling feel like data entry, the calls stop happening. His guy will do thirty quick logs. He won't do thirty long ones.

## What does this buy you?

Set the calls up as research and a few things fall out of it for free. You find the handful of leads that are still alive and ready to move. You build a script from real objections instead of imagined ones. And you get a clean read on whether your lead problem is a closing problem or a speed problem — two different fixes, and most owners guess wrong about which one they have.

There's a second payoff most people miss. Every one of these calls is a small reputation touch. A customer who got ghosted nine months ago and then got a friendly call asking what happened remembers that, even if they bought elsewhere. You're cleaning the list and repairing a few relationships at the same time.

The contractor's plan now is simple. Pull the oldest leads first. Start dialing the ones from last fall. Log the category, offer the follow-up, ask for the referral. Run the recordings through transcription on Friday and rebuild the script for the next week.

He's starting Monday with the oldest name on the list — a crawl-space quote from last fall that's been sitting untouched since the day it came in.

### Business Coaching vs. Consulting: What's the Actual Difference?
Published: 2026-06-16 · 5 min read · Tags: Coaching, Business Strategy
URL: https://igniumconsulting.io/blog/business-coaching-vs-consulting

> Business coaching and consulting solve different problems. A consultant tells you what to do and leaves. A coach sits with you while you figure out why you haven't done it yet — and then makes sure you do.

A consultant tells you what to do. A coach sits with you while you figure out why you haven't done it yet — and then makes sure you do. That's the short version. The longer version is messier, because in practice the line between the two barely exists.

I get asked this question a lot, usually by someone who's trying to figure out which one they need. The honest answer is that most business owners who hire a consultant actually need a coach, and most people who hire a coach wish their coach would just tell them what to do. The problem isn't the label. The problem is that nobody explains what you're actually buying.

## What Does a Business Consultant Actually Do?

A consultant comes in with a specific deliverable. Audit your operations. Build a financial model. Design a marketing strategy. Write the playbook. Hand it over. Leave.

The good ones are worth every dollar. They see patterns you can't see because you're inside the thing. They've done the same work for ten other companies in your industry and they know what works. You're paying for their expertise applied to your situation, packaged into something you can execute.

The problem is the last part. You can execute. Most business owners I work with have a drawer full of strategies and playbooks from consultants. Beautiful documents. Smart recommendations. Sitting in a folder somewhere collecting dust. Not because the advice was wrong — because nobody stuck around to make sure it got done.

## What Does a Business Coach Actually Do?

A coach doesn't hand you a playbook and leave. A coach shows up every two weeks and asks why you didn't do the thing you said you were going to do. And then sits with you while you figure out whether the problem is tactical or personal — because it's almost always both.

The owner who won't raise prices isn't facing a pricing problem. She's facing a confidence problem dressed up as a pricing problem. The founder who can't delegate isn't missing an org chart. He's missing the ability to let go of control long enough to let someone else fail and learn. A consultant would build the org chart. A coach would figure out why you won't use it.

That's the real difference. Consulting is expertise delivery. Coaching is behavior change with accountability.

## Why the Line Barely Exists Anymore

Here's where it gets complicated. The best coaches consult. The best consultants coach. Anyone who tells you these are completely separate disciplines hasn't done either one for very long.

I open QuickBooks in my coaching sessions. I run P&L analysis, do job costing, calculate margins. That's consulting work. But I do it sitting next to the owner, walking them through what the numbers mean, so they can make the decision themselves next quarter without me in the room. That's coaching.

One of my clients calls me her business therapist. I'll take it. Because that's closer to what actually happens than either "coach" or "consultant" captures. We talk about the business. We talk about why she's not sleeping. We pull up the spreadsheet and figure out which clients are profitable and which ones are draining her team. Then we make a plan and I hold her to it.

If you forced me to draw the line, it would be this: a consultant is done when the deliverable is done. A coach is done when the behavior has changed.

## How to Know Which One You Need

If you know exactly what's wrong and you need someone with specific expertise to fix it — hire a consultant. You need a new CRM implemented, your books restructured, a go-to-market strategy for a new product. Scoped project, clear deliverable, defined timeline.

If you know something is wrong but you can't quite name it — or you can name it but you keep not fixing it — that's a coach. You're stuck. You're overwhelmed. You're making decisions reactively instead of strategically. The business grew past your ability to manage it the way you used to, and you haven't built the systems or the team to catch up.

Pretty much every founder I work with starts with the second one. They think they need a strategy. What they actually need is someone who will sit across from them every two weeks and not let them hide from the hard stuff.

## What to Watch Out For

The coaching industry has a reputation problem, and it's earned. There are a lot of people charging premium rates to ask you how you feel about your goals and then schedule another session. No accountability, no operational knowledge, no willingness to open the books and look at what's actually happening.

If your coach has never looked at your P&L, never asked about your margins, never pushed back on a decision you were excited about — you don't have a coach. You have an expensive friend.

On the consulting side, watch for the deliverable-and-disappear model. A beautiful strategy deck means nothing if nobody is there three months later to ask whether you implemented it. The best consulting engagement includes some version of follow-through, even if it's just quarterly check-ins.

## The Version That Actually Works

The engagement that works best for most small business owners is the one nobody markets: coaching with consulting teeth. Someone who knows enough about operations, finance, and systems to give you real tactical advice — and who shows up consistently enough to make sure you actually use it.

That's what I do. I don't have a name for it that fits on a business card. Business therapist is the closest anyone's gotten.

A client told me last week she'd known for six weeks that she needed to have a pricing conversation with her biggest account but kept pushing it off. We spent twenty minutes on the coaching side — why she was avoiding it, what she was afraid of — and twenty minutes on the consulting side — here's exactly how to structure the conversation, here are the two options to present, here's who should be in the room. She had the call the next day. It went fine.

Six weeks of avoidance, forty minutes to fix it. That's what the combination looks like.

### You're Probably Losing Money on Two or Three Clients Right Now
Published: 2026-06-12 · 4 min read · Tags: Job Costing, Agency Profitability, QuickBooks
URL: https://igniumconsulting.io/blog/client-profitability-job-costing-agency

> Most agency owners think they know which clients are profitable, but their P&L is lying to them. Here's how to run a simple job costing exercise in QuickBooks that shows the real number — and what to do once you see it.

Most agency owners I talk to can tell me their monthly revenue and roughly what they pay in payroll. What they can't tell me is which clients are actually making them money.

That's not a character flaw. It's a bookkeeping problem.

## Why Your P&L Isn't Telling You the Full Story

Here's what I keep seeing: labor costs sitting in overhead. Client-specific software subscriptions treated the same way as the owner's phone bill. Time that gets logged but never matched against what a specific client is actually paying.

The P&L says the business is doing fine — maybe 40–50% gross margin on paper. But that number is meaningless if you're blending profitable clients with clients you're subsidizing and calling it a win.

When I pull up QuickBooks with an agency owner and we start moving things around — contractors who work exclusively on one account, software that only runs because that client exists, hourly labor billed to specific projects — the picture changes. Quickly.

## The $630 Problem

I was in a session recently with an agency owner doing about $650K projected for the year across roughly 24 clients. Her QuickBooks had a clean-looking overhead bucket and a P&L that looked solid on the surface.

We did one thing: took her total overhead for May, divided it by 24, and got a per-client burden of about $630 a month. Then we added that $630 to her real labor cost for one of her mid-tier clients — a client she thought was paying reasonably well.

She was losing money on that client. Not barely breaking even. Losing money. And she'd had them for over a year.

The $630 allocation wasn't the problem — overhead is real and it has to live somewhere. The problem was she'd never run the calculation. Once we did, she could see exactly what it would take to hit 20% margin on that account: either fewer hours or a price increase.

## What Counts as COGS and Why It Matters

This is the one that trips people up the most. COGS — cost of goods sold — should only include costs that vary directly with the work you do for clients. The moment you change the client list, those costs change too.

That means: contractor labor on client projects, yes. Client-specific software subscriptions, yes. Hourly team time billed to accounts, yes. Your own salary as the owner, your office lease, your general marketing spend — those stay in overhead.

When you miscategorize variable labor as overhead, your gross margin looks lower than it is, your overhead looks higher than it is, and your per-client job costing numbers are fiction. The CPA will usually follow whatever you give them. It's worth a conversation where you walk through each line item and ask: does this exist because of a specific client?

## The Fix Is Not a New Tool

You don't need different software. You need one month of clean data.

Pick a recent month where you have most of your transactions coded. Export a client-level time report from whatever you use for time tracking. Put your total overhead next to it, divide by number of active clients, and add that to each client's actual labor cost. Now you have a rough profitability number per account.

It's not a perfect model. But it's dramatically more useful than what most agencies are operating with, which is a blended margin number and a gut feeling about which clients feel like they're worth it.

The ones that feel hard are usually the ones losing you money. The numbers tend to confirm what you already suspected.

## What You Do With the Number

Once you have real job costs per client, you've got three options for any account that's below your target margin: reduce hours, raise the price, or decide it's a strategic exception and be honest with yourself about why.

Most agency owners know which clients they're undercharging. They've been hoping the relationship would evolve, or they haven't had the margin math to make the conversation feel concrete. Once you can show a client that your costs are $X and your current fee leaves you at 8%, the conversation changes.

You're not asking for a favor. You're showing them the math.

## Start With May

If you're going to do this, pick one completed month — last month works — and make it your baseline. Code everything. Get your bookkeeper to reconcile it. Then run the per-client allocation.

Don't try to do a year at once. You'll get overwhelmed and you won't finish. One clean month tells you everything you need to know to make decisions right now.

The agency owner I mentioned is auditing the full year now — but we started with one month, found the client that was bleeding money, and made one pricing decision. That's the model.

Ignium Consulting works with agency owners and service business founders on financial clarity, delegation, and building the systems to scale without burning out. If you want to go through this kind of exercise on your own numbers, [reach out](https://igniumconsulting.io).

### When Your Retainer Client Keeps Adding Work
Published: 2026-06-11 · 4 min read · Tags: Scope Creep, Retainer Management, Agency Growth
URL: https://igniumconsulting.io/blog/retainer-scope-creep-agency

> When a client's requests outgrow their retainer, most agency owners absorb the extra work and say nothing. Here's what to do instead — document scope, present explicit options, and have the pricing conversation before resentment sets in.

An agency owner I work with has been running influencer activations for a food brand client at roughly double the rate her retainer covers. Not because the client is unreasonable — because nobody documented how many were included.

This happens in almost every agency I've talked to. A retainer gets signed, the work starts, the client gets excited, and the requests multiply. Nobody wants to have the awkward conversation, so the team absorbs it. Six months later the account is quietly unprofitable and everyone is burned out.

## How does scope creep actually start?

It usually starts with a yes that seemed fine at the time. The client asks for one more activation, one more deliverable, one more revision. You say yes because the relationship is good and you want to keep it that way. Then that yes becomes the new baseline, and before long the new baseline gets its own set of extras.

In this case, the client had budget for more influencer content — they were genuinely interested in expanding — and that made it easy to keep saying yes. But intent and scope are two different things. Wanting to grow the account isn't the same as agreeing to pay for the additional work.

## Why most agencies don't catch it early

The people doing the work rarely have visibility into what was originally agreed. The account manager knows, maybe. The person managing the influencers probably doesn't. So the team just keeps executing, nobody flags the discrepancy, and by the time someone runs a profitability check the gap is substantial.

There's also a relational pull at play. Most agency owners got into this business because they like their clients and they like doing good work. Protecting scope feels adversarial. It's not.

## What to do when you're already over scope

The conversation needs to happen before the resentment sets in — on either side. Once you're doing significantly more work than you're charging for, you're not doing the client a favor. You're building toward a situation where you'll eventually have to raise your rates dramatically, drop the account, or tell them you can't sustain the current service level. None of those are clean options.

What works better is presenting two explicit choices: reduce the monthly deliverables to what the retainer covers, or renegotiate pricing to reflect the actual work being done. Neither option is "I've been doing you a favor and now I'm charging you for it." The framing is cleaner — here's what we agreed to, here's what we've been doing, here's how we want to move forward.

In this case, the client actually has budget for the expanded work. The friction point was never the money — it was that no one had documented the scope clearly enough to make the conversation possible.

## Who should have the pricing conversation?

Not always the agency owner. This is counterintuitive for founders who default to handling everything client-facing themselves.

In this situation, the agency owner held the client relationship and controlled the narrative, but had her account lead run the pricing conversation directly. That separation keeps the relationship intact. The agency owner is still the person the client trusts; the account lead handles the mechanics of renegotiation. Mixing those roles can make clients feel managed rather than supported.

One thing that matters: whoever isn't involved in the pricing conversation should be kept out of that meeting. Don't bring someone with a warm relationship to the client contact into a discussion about money — it muddies the dynamic and creates loyalty conflicts neither party knows how to resolve.

## The scope document you should have had from the start

The fix going forward is simple to describe and slightly tedious to actually do: define the number of activations, deliverables, and revision rounds in writing before the work starts. Tie each line item to a unit. "Influencer management" is not a scope. "Six influencer activations per month with one round of revisions each" is a scope.

When scope is vague, clients aren't necessarily trying to extract more than they're paying for. They're operating on whatever mental model they built from the sales conversation. If your pitch implied more than your contract specified, that's a contract problem.

For retainer clients you already have, treat the scope conversation as a reset. Review what's been delivered against what was agreed and use that as the opening for a clean renegotiation. Do it before the account gets to a place where you're quietly resentful or they're suddenly surprised.

## The operational signal nobody's watching

The scope problem wasn't the only thing that surfaced. When an account grows faster than the team executing it, the execution gaps compound. A scheduler stretched past capacity missed a meeting and made two approval errors in the same week. The fix wasn't to reprimand her — the role required two people and had been running with one.

The tell is usually a rash of small errors. Not catastrophic failures, just slippages that show up more frequently than they used to. That's the signal that the current structure isn't keeping pace with the account load.

The agency owner is posting a backup scheduler on Upwork this week. The assignment she's using to evaluate candidates specifically tests for manual community engagement — no AI shortcuts — because the role requires authentic interaction that bots replicate badly. That one sentence in the job post will filter out about 80% of the applicants, which is exactly the point.

### Scope Creep Doesn't Start With the Client
Published: 2026-06-09 · 4 min read · Tags: Client Management, Pricing
URL: https://igniumconsulting.io/blog/scope-creep-doesnt-start-with-the-client

> Scope creep rarely starts with a demanding client. It starts with a vague retainer and no documented deliverable count. Here's how to fix it.

Scope creep in service businesses almost never starts with a difficult client. It starts with a retainer that doesn't say how many deliverables are included per month. The client asks for one more thing. Then another. And because nobody wrote down the number, nobody knows when the line got crossed.

I was on a coaching call yesterday with the owner of a marketing agency. She has a client paying a solid monthly retainer for social media and influencer content. Good account. Good relationship. But over the past two months, the client started requesting daily influencer activations on top of the agreed deliverables. Her team was fulfilling every request because the scope document didn't specify a cap.

## How Does Scope Creep Actually Start?

The pattern is the same almost every time I see it. The original agreement says something like "social media management and influencer content" without a number attached. The client reasonably assumes that means whatever they need. The team reasonably assumes they should deliver whatever is asked. Both sides are operating in good faith inside a vague agreement. That's the whole problem.

By the time somebody notices, the team is doing 40% more work than the retainer covers. And the owner is stuck choosing between eating the margin or having an uncomfortable conversation with a client who doesn't think they've done anything wrong. Because they haven't.

## What to Do Before the Client Call

The fix isn't confrontation. It's documentation. Before you have any conversation with the client, you need three things written down: what's included in the current retainer, how many units of each deliverable per month, and what the cost would be for the extra work they've been getting.

In this case, we walked through every deliverable the team had produced in the last 60 days and compared it to what the retainer was priced for. The gap was obvious once it was on paper. The team was producing roughly double the influencer activations the retainer was built to cover.

## Two Options, Not One Ultimatum

The move that works is giving the client two clear options instead of one awkward ask. Option one: we reduce the monthly deliverables to match the current retainer. Option two: we adjust the retainer to cover what you've actually been receiving. Both options are reasonable. Neither one makes the client feel like they've been doing something wrong.

The owner who controls the relationship should set the agenda. The person who owns the pricing rationale should lead that part of the conversation. Don't let your whole team sit in on the pricing discussion — keep it between the people who can actually make decisions.

## Why Getting Ahead of It Matters

The worst version of this conversation is reactive. The client sends another request, your team pushes back for the first time, and now the client feels like something changed. They didn't get a warning. They got a wall.

The better version is proactive. You send a short note before the next call: "I want to make sure we're aligned on scope — I'm going to walk through what's included and what's been added so we can make sure the priorities match the budget." That single sentence reframes the entire conversation from "you're asking too much" to "let's make sure we're on the same page."

## The Real Fix Is Upstream

After we sorted out the client conversation, we went back to the retainer template. Every new agreement now specifies the exact number of deliverables per month per category. Not a range. A number. If the client wants more, there's a documented rate for additional units.

It takes about ten minutes to add that specificity to a proposal. It saves about ten hours of awkward conversations per year per client.

The agency owner told me she'd known about the scope issue for six weeks but kept pushing it off because the client relationship was good and she didn't want to rock it. Six weeks of extra work her team wasn't getting paid for, because the original document was three sentences too short.

### The Number That's Missing From Your Marketing
Published: 2026-06-08 · 4 min read · Tags: Financial Clarity, Marketing
URL: https://igniumconsulting.io/blog/the-number-thats-missing-from-your-marketing

> Most small businesses track leads and revenue but skip the number that actually matters: close rate by source. Without it, you're guessing.

Most small businesses can tell you two things: how many leads came in and how much money they made. What they almost never know is which leads turned into money. That gap — close rate by source — is where every bad marketing decision gets made.

Here's what I see pretty much every time. Revenue is up. The owner is feeling good. Google Ads brought in ten leads. Organic search brought in ten leads. Great month. But which of those twenty leads actually signed? Which ones paid? Nobody knows. The spreadsheet tracks where they came from. It tracks who became a client. But those two columns don't talk to each other.

## Why Close Rate by Source Changes Everything

Lead count is flattering. Close rate by source is useful. Those are different things.

You can have a channel that generates a ton of leads and closes almost none of them. You can have another channel that trickles in three leads a month and closes every single one. If you're only counting leads, you'll pour money into the first channel and starve the second. You'll feel productive the entire time you're doing it.

The math isn't complicated. But the tracking requires a specific, unsexy step: marking which leads actually paid, right there in the same place you recorded where they came from. Not in a different tab. Not in your head. Not "we'll figure it out later." Same spreadsheet. Same row. Source on the left, paid on the right.

## The Dashboard That Lies to You

Traffic metrics are the worst offenders. I've seen months where direct traffic to a site dropped off a cliff. The analytics dashboard looked like something was broken. And revenue hit a record. The owner was staring at a report that said the sky was falling while the bank account said otherwise.

That contradiction makes people crazy. And the instinct is to trust the dashboard because it has charts and numbers and looks official. But the dashboard is measuring activity, not outcomes. A hundred website visitors who don't buy are worth less than three who do.

The uncomfortable truth is that most marketing reports measure how busy your marketing is, not how effective it is. Impressions, clicks, cost per click, traffic volume — all activity metrics. The only question that matters is: did they pay?

## The Ad Spend Trap

Here's where it gets expensive. Say you bump your ad spend by five hundred bucks a month. Your cost per click goes up. Your marketing person sends you a report that looks worse than last month. But you had a record revenue month.

What happened? You probably got better quality leads. Fewer of them, maybe. More expensive per click, sure. But the ones who showed up were ready to buy. You'd never know that from the ads report. You'd only know it if you tracked which of those ad leads actually closed.

Without close rate by source, you can't answer the most basic question in marketing: should I spend more or less on this channel? You're just guessing. Educated guessing, maybe. But still guessing.

## How to Actually Track It

The fix is boring. Add two columns to whatever you're using to track leads. One for "agreement signed." One for "invoice paid." That's it. Now you can filter by source and see your close rate for each channel.

Most people resist this because it feels like extra work for their admin person. It is extra work. About thirty seconds per lead. And it's the difference between knowing where your money comes from and hoping you'll figure it out eventually.

Once you have even two months of this data, patterns emerge fast. You'll see that one channel closes at forty percent and another at eight percent. You'll stop agonizing over whether to increase ad spend because the numbers will just tell you.

## The Confidence Problem

The real cost of not tracking close rate by source isn't wasted ad dollars. It's the constant second-guessing. Every month becomes a referendum on whether your marketing is working. Good month? Must be the ads. Bad month? Maybe we should cut the ads. There's no foundation under any of it.

And when someone asks you — your partner, your accountant, yourself at 2 AM — whether your marketing spend is worth it, you shrug. Not because you're bad at business. Because you skipped one column in a spreadsheet.

Two columns, thirty seconds per lead, and you stop shrugging.

### Job Costing Saved the Agency (After It Almost Killed It)
Published: 2026-05-22 · 7 min read · Tags: Financial Clarity, Agency
URL: https://igniumconsulting.io/blog/job-costing-saved-the-agency

> A 15-person agency was losing money on half its clients and didn't know it. Here's how we rebuilt the pricing model in 6 weeks.

The owner thought they were running a 22% margin business. Their bank account disagreed.

## The diagnosis

We pulled the last twelve months of QuickBooks data, tagged every employee hour by client and service line, and ran the actual cost-of-delivery against each invoice. Half of their flagship retainers were break-even or worse.

This is exactly the kind of work I walk through inside [Financial Clarity](/#approach) engagements — opening the books in real time so decisions stop being feelings.

## The fix

Three moves, in order:

  - Time guardrails on every service tier — a hard ceiling, not a soft target.

  - Re-priced two unprofitable client cohorts. We lost one. We expected to lose two.

  - Margin reviewed monthly with the ops lead, not annually with the accountant.

## The result

40% gross margin target hit in 90 days. The owner stopped subsidizing clients with her own salary.

### How to Extract the Founder in 4 Months
Published: 2026-05-05 · 9 min read · Tags: Systems, Delegation
URL: https://igniumconsulting.io/blog/extracting-the-founder

> Most founders are the bottleneck and the brand. Pulling them out of delivery without losing the client relationship takes a system, not willpower.

The PR firm owner I worked with was running every client call, writing every pitch, and approving every send. She wanted to launch a productized service. She had no hours to launch it.

## Step 1: Decide what only the founder can do

Strategy. Senior relationships. Hiring the next senior person. Everything else is delegable on a timeline.

## Step 2: Build the layer

Ops manager hired in week three. 30/60/90 onboarding plan modeled after the playbook I describe in [Scalable Systems](/#approach). Escalation map written so the team knew exactly when to interrupt her and when not to.

## Step 3: Stay in the ring

Weekly 1:1s with the ops manager for the first 60 days. I sat in for the first three. By month four, the founder was on enterprise pitch calls instead of QA-ing newsletters.

### $72K in AI Savings Without the Hype
Published: 2026-04-18 · 6 min read · Tags: AI, Operations
URL: https://igniumconsulting.io/blog/ai-72k-without-the-hype

> I deploy AI tools daily and implement them for clients. Here's the unsexy reality of what actually saves money versus what just sounds good in a keynote.

Most "AI strategy" decks are a list of vendors. Real savings come from boring automation around three workflows.

## Reporting

A digital agency was burning 18 hours a week building client performance reports by hand. We piped Google Ads + GA4 into a templated Claude workflow. 18 hours became 30 minutes of review.

## Ad management

Daily bid checks and creative rotation triggered by performance thresholds. Mid-level media buyer freed to do the work that needs judgment.

## Data extraction

PDF invoices and onboarding intake forms parsed straight into the CRM. Onboarding lead time cut in half.

This is the kind of thing I cover inside [AI-Powered Operations](/#approach) — implementation, not theater.

### Stop Ending Sales Calls Without the Next One Booked
Published: 2026-08-13 · 4 min read · Tags: sales follow-up, pipeline management, case studies
URL: https://igniumconsulting.io/blog/schedule-next-call-before-proposal-goes-cold

> A big pipeline that isn't closing is usually a follow-up problem, not a lead problem. Booking the next call before the first one ends, and backing your pitch with specific case stories instead of promises, turns stalled proposals into signed contracts.

A PR agency owner I coach showed up to our session with nine inbound calls from the past week and roughly $250,000 sitting in outstanding proposals. That sounds like a lead problem solved. It's actually a warning sign. A pipeline that size usually means somebody stopped chasing the close.

## Why does a full pipeline stall before it closes?

Most of the founders I talk to treat the proposal as the finish line. They send the PDF, thank the prospect for their time, and wait. The prospect gets busy, the email drops to page three of their inbox, and three weeks later nobody remembers who was supposed to follow up.

The fix isn't a better proposal template. It's ending every single sales call with the next call already on the calendar, before you hang up. Not "I'll follow up next week" — an actual time, confirmed on both ends, before the conversation is over. My client walked out of our session with a rule: no sales call ends without a second one booked, full stop.

That one habit changes the math. A proposal with a scheduled review call gets read. A proposal that just sits in someone's inbox gets forgotten, not because the prospect changed their mind, but because nobody gave them a reason to open it again.

## What do you sell when you can't guarantee the outcome?

PR is a hard sell because nobody can promise a placement. My client can't tell a prospect "you'll get covered by this outlet by this date," and prospects know that. So the pitch can't lean on promises. It has to lean on proof.

We talked through building four or five specific case stories — real campaigns, real outcomes, told with enough detail that a prospect can picture their own business in the story. Not a logo wall. A story with a start, a problem, and a number at the end. When you can't guarantee the result, the next best thing is showing someone you've gotten that result before, for a business that looked a lot like theirs.

Alongside the stories, she's leaning on activity metrics she can guarantee — number of pitches sent, media contacted, follow-up cadence — as a way to be transparent about effort even when she can't be transparent about outcome. Prospects respond better to "here's exactly what we do every week" than to vague reassurance.

## Do you need a different pitch for every prospect?

Not every prospect, but at least two versions. Someone who's never worked with an agency before is nervous about a different thing than someone who got burned by their last agency. The first person needs to understand what they're buying. The second person needs to hear, directly, why this time will be different.

We split her talk track into those two versions. For the first-timer, more explanation of process and what to expect month one. For the burned prospect, more direct acknowledgment of what usually goes wrong with agencies and how her team avoids it. Same core offer, two different openings, because the objection each person is silently sitting on is different.

## What's the real cost of skipping the follow-up?

The deals that say no rarely hurt a pipeline. The ones that never get an answer are the expensive ones, because they sit on the books looking like revenue while doing nothing. My client had a $7,500 scoped proposal from a VC-introduced founder that almost went quiet simply because nobody circled back after the initial excitement wore off. She caught it, negotiated the scope down to something that fit his budget, and closed it. That's the one she caught.

Somewhere inside that $250,000 in outstanding proposals are a few more like it — not lost, just unattended. She's also sitting on an $8,500-a-month scope she had to defend line by line, walking the prospect through hours and team costs so the number made sense against the return. That conversation only worked because she picked up the phone a second time instead of waiting for the prospect to make the next move.

The founders I talk to who fix their close rate rarely do it by writing better proposals. Most of their proposals were already fine. They do it by refusing to let a good conversation end without a next one already on the calendar, and by tracking close rate and sales velocity as actual numbers instead of a gut feeling about how the quarter is going. You can't fix a leak you haven't measured.

There's a second, quieter cost too: capacity planning gets harder when nobody knows which proposals are actually live. If three of those outstanding deals close in the same month, staffing has to scale fast. If they're all cold and nobody's said so out loud, the business plans around revenue that was never coming.

By the end of our session, she had nine inbound leads from the week, two more calls already on the calendar, and a standing rule that the next nine conversations don't end without a follow-up time attached before anyone says goodbye.