Positioning Research

Stop losing time, customers, and jobs between people and systems.

Not because anyone’s dropping the ball on purpose - because nothing in the system tells anyone whose ball it currently is.

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

Does this sound familiar?

You might recognize:

“We send a quote and then just go silent.”

“An inquiry comes in and somehow nobody follows up.”

“A customer has to repeat information they already gave us.”

“Nobody’s totally sure what stage a job is actually at.”

“We keep track of things in more than one place, and they don’t agree.”

“Work stalls because nobody’s clear on whose turn it is next.”

It might not be what it looks like

Lost work is usually a visibility problem, not a communication problem

The instinct is “we just need people to communicate better” - someone should have said something, someone should have followed up. That reads as a people problem, so the fix feels like it should be a people fix: more check-ins, more reminders, more discipline.

Usually, though, nobody forgot anything on purpose. The repeated misses may be caused by the workflow itself lacking clear ownership, visible state, and reliable transitions between people and systems - there was never a single, trustworthy answer to "what stage is this at, and whose turn is it next?"

Diagnosing the workflow, not the people in it, means looking at the handoff: what has to happen for work to move from one person or step to the next, and what happens today when that handoff has no clear owner or no visible status.

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 professional-services firm gets a steady stream of inbound inquiries through its website and referrals, but a portion never receive a reply at all - not because anyone decided not to respond, but because there’s no single place all inquiries land, so some sit unseen in an inbox nobody’s consistently checking.

What Ihsan would inspect

Every place an inquiry can currently arrive, and what happens to it after it lands
Whether there’s a single, visible owner for “respond to new inquiries” or whether it’s informally shared
How status is currently tracked, if it’s tracked at all, between first contact and a decision

Possible interventions

Connect the inquiry sources into one place instead of several scattered inboxes
Clarify ownership so a specific person - or a clear rotation - is responsible for every new inquiry
Standardize a simple status so it’s visible whether something has been responded to, not assumed

What should improve

Fewer inquiries going unanswered, and a clear, checkable answer to “did we follow up on that?” instead of a guess.

Bring the part of the business that’s stuck

Bring the thing that keeps slipping between people or systems. 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.