Positioning Research / Experimental
Positioning Experiments
Internal index of front-door and offer experiments used in real prospect conversations. Not Ihsan Systems’ permanent services menu, and not linked from primary navigation. The homepage direction has been decided and is still being refined (see Homepage below) - no problem-framing, methodology, or offer winner has been chosen yet.
Ten active experiments and two archived reference pages are registered here. See docs/positioning-experiments.md for the full experiment log, the controlled-experiment rules, and the prospect-interview template used alongside these pages.
Homepage
Tested a full alternative homepage layout - simpler, problem-first, no systems-model teaching required before a visitor understands or contacts Ihsan - against the previous homepage. On 2026-08-17, after thirteen refinement passes, "Work Shouldn’t Be This Hard" was promoted to production `/` for the first time. Unlike the other groups here, this one doesn’t freeze once promoted: refinement continued directly on the route (hero recomposition, ambient animation, capability marquee, What to Expect section), and on 2026-08-18 the current state was promoted to `/` again. The route stays live as the ongoing staging/candidate page for whatever comes next, rather than being archived once "won." The compressed variant was not promoted (it tested minimalism as a separate variable and is kept live for reference). Both earlier production homepages are archived, not deleted: the original framework-first homepage at /homepage-framework, and the intermediate Redesign/Integrate/Automate-trio-hero homepage at /homepage-previous.
Work Shouldn’t Be This Hard
/work-shouldnt-be-this-hard- Hypothesis
- A homepage told as one simple story - a belief, a three-part Redesign/Integrate/Automate intervention trio with Build as a supporting capability (not a fourth peer), where problems usually show up (Grow/Flow/Keep), and a low-friction next step - creates stronger commercial understanding than a framework-first homepage, with methodology kept deliberately small.
- Audience / situation
- An owner/operator who knows something is frustrating, manual, unreliable, fragmented, or harder than it should be, but doesn’t know if the answer is process, software, integration, automation, AI, or a custom build - and shouldn’t need to know.
- Belief transition being tested
- “I need to understand how Ihsan sees a business before I understand what Ihsan does” becomes “I understand what Ihsan believes, what they do, and where in my business it might apply - as one story, not a framework to learn.”
Work Shouldn’t Be This Hard — Compressed
/work-shouldnt-be-this-hard-simple- Hypothesis
- The same positioning, with less information shown, produces stronger comprehension and a clearer next action than the fuller original.
- Audience / situation
- Same as the original variant - the audience is deliberately held constant. Only information density changes.
- Belief transition being tested
- "Explaining more builds more trust" becomes "showing less, more clearly, gets the same idea across faster."
Previous Homepage (Redesign/Integrate/Automate)
/homepage-previous- Hypothesis
- N/A - this is the archived intermediate production homepage (the result of the first promotion), not an active hypothesis under test.
- Audience / situation
- N/A - preserved as research material and a comparison baseline for the current candidate.
- Belief transition being tested
- N/A - kept for comparison, not currently being tested against anything.
Previous Homepage (Framework-First)
/homepage-framework- Hypothesis
- N/A - this is the archived original production homepage, not an active hypothesis under test.
- Audience / situation
- N/A - preserved as research material and a comparison baseline.
- Belief transition being tested
- N/A - kept for comparison, not currently being tested against anything.
Problem framing
The five controlled front-door experiments. Design, CTA, section order, intervention ladder, and methodology-preview treatment are held constant across all five - only the front-door problem language varies. These test which problem creates recognition, not which page is most persuasive.
Too Much Effort
/too-much-effort- Hypothesis
- Operational friction, framed broadly, is the widest possible front door.
- Audience / situation
- Owners and teams doing manual work that feels disproportionate to its value.
- Belief transition being tested
- Some work requires real judgment. Some work only exists because the operating system is poorly designed.
Growth Shouldn’t Be Harder
/growth-shouldnt-be-harder- Hypothesis
- Growth-related operational friction is the strongest front door.
- Audience / situation
- Owners whose admin, coordination, and mistakes have grown faster than revenue.
- Belief transition being tested
- “More admin is just the price of growth” becomes “some of this burden is caused by how work, information, ownership, and tools are structured.”
Everything Runs Through Me
/everything-runs-through-me- Hypothesis
- Owner dependence is a stronger recognition trigger than generic efficiency talk.
- Audience / situation
- Owners who are still the default routing layer for routine decisions and information.
- Belief transition being tested
- “I need to stay involved because I know the business best” becomes “routine work depends on me because ownership, visibility, or decision rules are missing.”
Before You Hire
/before-you-hire- Hypothesis
- Hiring pressure is a strong, budget-adjacent moment to intervene before a recurring cost is committed.
- Audience / situation
- Owners whose team is asking for another hire to keep up with admin/coordination load.
- Belief transition being tested
- “We’re overloaded, so we need another person” becomes “we should know how much of this is real capacity demand versus workflow-created labor first.”
Falling Through the Cracks
/falling-through-the-cracks- Hypothesis
- Lost work / reliability / handoff failure creates stronger commercial recognition than general efficiency messaging.
- Audience / situation
- Owners losing inquiries, follow-ups, or status visibility between people and systems.
- Belief transition being tested
- “We just need people to communicate better” becomes “misses may be caused by the workflow lacking clear ownership and visible state.”
Methodology
Tests whether additional methodological depth increases trust once a visitor already recognizes their problem - not a sixth problem-framing variant, and not directly comparable to that group.
Offer
Tests which first-offer framing a prospect prefers, not which front-door problem resonates - a different hypothesis category from the two groups above.
Assessment Experiment
/assessment-experiment- Hypothesis
- Prospects prefer paying for a bounded diagnosis first, with implementation as a separate later decision.
- Audience / situation
- Prospects ready to pay for clarity before committing to a fix.
- Belief transition being tested
- Understanding-first is a viable, sellable first engagement on its own.
Workflow Sprint Experiment
/workflow-sprint-experiment- Hypothesis
- Prospects prefer a single bounded engagement that both diagnoses and improves the workflow.
- Audience / situation
- Prospects who want the fix, not just the findings, from the first engagement.
- Belief transition being tested
- Outcome-oriented bundling is a stronger first offer than diagnosis alone.