Positioning Research

Your business shouldn’t get harder to run every time it grows.

More customers, more jobs, more employees - but somehow disproportionately more admin, more coordination, more mistakes, and more of you.

Tell me what’s getting stuck See how Ihsan approaches it

Does this sound familiar?

Owners in this spot tend to say things like:

“We’re busier than ever, but it doesn’t feel like we’re actually further ahead.”

“Every new customer means more chasing, not just more revenue.”

“Things slip through more often now than they did when we were smaller.”

“We hired more people and it still gets chaotic.”

“I spend weekends catching up on things that should’ve happened during the week.”

“Growth is creating more work to manage, not more profit.”

It might not be what it looks like

Growth should create more capacity, not just more work

It’s easy to treat more admin, more coordination, and more owner involvement as simply the price of growth. Every business gets more complicated as it gets bigger, so the assumption feels reasonable.

But some of that burden may come from how work, information, ownership, and tools are structured - not from growth itself. A workflow that was fine at last year’s volume doesn’t automatically keep up at this year’s. When it doesn’t, growth starts costing capacity, quality, customer experience, and owner time all at once, instead of paying for itself.

That’s a different problem than “we grew too fast,” and it usually has a different fix - not necessarily more people or more software, but a workflow that was never rebuilt for the volume it’s now carrying.

Our approach

Find the constraint before choosing the fix

We don’t start with a preferred technology. Once the real constraint is clear, the right move is usually one of these, roughly in order of how much change it introduces:

SimplifyStandardizeConfigureConnectAutomateBuild

Or build nothing, if that's the right answer. We determine what should change and implement it - not just recommend it.

How we see a business

We look at the business as a connected system

A business moves through a lifecycle: Grow (turning opportunity into a customer), Flow (getting the work done and paid for), and Keep (staying in the relationship after the job ends). A problem that shows up in one place often started somewhere else in that chain.

See how we think about this

Example scenario

Hypothetical, for illustration only - not a claimed result from a real client.

What is happening

A specialty contractor doubled its job volume over two years. Revenue grew, but so did the owner’s hours - more scheduling conflicts, more callbacks about job status, more evenings spent reconciling what actually happened on-site with what got invoiced.

What Ihsan would inspect

How a job moves from booked to scheduled to completed to invoiced, and who owns each handoff
Where job-status information lives, and how many places it has to be re-entered
Which decisions still route through the owner by habit rather than necessity

Possible interventions

Standardize the handoff between field and office so status doesn’t depend on someone remembering to call it in
Configure the scheduling tool already in use so it’s the single source of truth, instead of a whiteboard plus a spreadsheet
Clarify who owns customer updates so the owner isn’t the default contact for “where are we on this?”

What should improve

Fewer status questions landing on the owner, fewer double-entered jobs, and a workflow that can absorb more volume without absorbing more of the owner’s time.

Bring the part of the business that’s stuck

Bring the part of the business that gets harder every time you grow. We start by understanding what is actually happening, not by pitching a fix.

Tell me what’s getting stuck

Or see how Ihsan approaches it first.