North Star Strategy
A diagnostic-led growth map for turning lead constraints and timing challenges into a sustainable, smoother software business.
From “Lead-Flow Constraint” to a Smoother, Durable Business
Make Polymorph less spiky and more durable — smoothing peaks and valleys while keeping the bar high on people, product, and profit.
- Lead flow is the constraint: self-rated 1/5 for volume, with 3/5 ICP fit and 4/5 reason-to-engage.
- Most work comes from referrals and search/LLM discovery; SDR experiments and random coffees have not converted.
- Concept design converts well, but pipeline into that step is thin and lumpy.
→ Tactics → Experiments
- A calibrated growth engine around high-trust channels: referrals, previous clients, and curated CEO/founder communities.
- Content, newsletter, and LLM SEO that keep Polymorph “top of mind” until buyers are ready.
- A productised retainer service that keeps relationships and revenue alive between large builds.
Who Polymorph Is When You Strip Away the Jargon
Polymorph has always been less about code and more about building the right thing first — combining upstream product thinking with deep technical delivery.
People-centred software that moves businesses forward
Use software to build more valuable, resilient businesses — not just more software. Reduce risk by doing the right upstream work before any code is written.
- Founders and leaders who can’t afford to build the wrong product twice.
- Internal teams that lack upstream discovery/UX and mobile depth, but still own delivery.
- Complex domains (energy, fintech, marketplaces, education) where requirements are ambiguous and stakes are high.
- Prospects drowning in developer jargon who need a plain-language, no-BS guide.
- Founder-led sales rooted in listening and pattern-matching, not pitch scripts.
- Evidence over ego: concept design and user validation are the default.
- Long-term partnerships preferred over one-off builds.
Build the Right Software Before You Write the First Line of Code
Most dev shops sell code. Polymorph sells clarity first — then builds the software that sits on top of it.
Paid concept design that “delivers hard” — surfacing blind spots, aligning stakeholders, validating user needs, and shaping a realistic pilot plan before any major build spend.
Discovery calls and proposals run by people who understand both technology and business constraints — no rigid SDR scripts, and no one-size-fits-all proposal templates.
The same posture behind the content (“Decoder”, “Translator”, “Red Flags”) shows up in sales: if custom software isn’t the right lever right now, Polymorph will say so.
Complex environments — from industrial energy monitoring to fintech and property — where UX, data, and infrastructure all need to work together without drama.
Tech-forward SA Product Companies Who Can’t Afford a Wrong Build
The best-fit buyers are mid-market businesses and funded scale-ups where product, engineering, and leadership all feel the risk of building the wrong thing — and want a partner who will push back intelligently.
Mid-market B2B and funded scale-ups (±R100m+ or VC-backed) with product/engineering leadership.
- Buyers: CEO, CTO, CPO, Head of Digital/Innovation.
- Pains: risk of wrong build; gaps in mobile/UX/product strategy.
- Outcomes: early product–market-fit signals; fewer rewrites.
Corporate innovation teams, complex portfolios (energy, property, logistics) needing an experienced partner.
- Strong fit when there's room for discovery and UX, not just "dev-only".
- Best when teams see Polymorph as an integrated product partner, not a code factory.
- Triggers: new funding, leadership changes, failed internal builds.
A Business With Strong Conversion Steps — and a Starved Top of Funnel
Concept design and delivery convert well. The constraint is simply not having enough of the right conversations at the right time.
What’s Been Tried, What’s Happening Now, and What Actually Works
This strategy is grounded in what the last few years have already taught Polymorph — not in wishful thinking.
4 meetings a week, for over a year, no work won. Right profiles, wrong timing, low trust.
Hard to track, hard to convert, easy to forget — even when people mean well.
The “you must do concept design this way first” posture created friction and limited flexibility.
Consistent messaging, repurposable into blogs, newsletters, and enablement — but not expected to be the primary growth lever.
Deep understanding of the buyer’s world, flexible proposal design, strong concept design conversion when people are ready.
2–2.5 month phase that aligns stakeholders, validates value, and often unlocks larger project work.
People who come through these channels arrive with context and intent — they already “get” some of Polymorph’s value.
Polymorph often tells prospects they are not ready to build; this creates long-term trust and future opportunities.
These phases build trust, reveal blind spots, and produce artefacts that help clients make better investment decisions — with or without an immediate build.
Two Tracks: Diagnostic & Build, and a Lower-&-Wider Retainer
These packages frame how Polymorph sells what it already does well — plus a new, lighter retainer that keeps relationships and learning alive before, between, and after projects.
- Solution strategy: target customers, underserved needs, value proposition.
- Market research: market size, competitor/alternative analysis, pricing context.
- Validated prototype: no-code clickable prototype tested with real users.
- Software architecture: high-level architecture aligned to current assets.
- Pilot plan: team, timeline, and investment estimate for the first release.
- Iterative development of the core product informed by the concept design.
- Close collaboration with internal teams and stakeholders.
- Analytics instrumentation for adoption and behaviour insights.
- Launch support and first-month stabilisation.
- Monthly strategy sessions with Patrick/senior team to stress-test ideas and roadmaps.
- Sanity checks on vendor quotes, architectures, and timelines.
- Lightweight experiments & prototypes to explore options without full builds.
- Priority access to Polymorph for when timing flips from “not yet” to “go”.
The Polymorph Growth Engine — All Framed as Hypotheses
Every channel is treated as an experiment: hypothesis → cost → learning. The mix optimises for trust, timing, and Patrick’s finite time.
- Systematise introductions from fractional CTOs, VCs, agencies who already trust Polymorph’s work.
- Design a simple, low-friction way for past clients and warm connections to surface new opportunities.
- Arm referrers with 1-page explainers and stories that make it easy to pitch Polymorph internally.
- Use the retainer product as an easier starting point for “not-yet-ready” referrals.
- Shift from random coffee networking to highly curated communities like Civitas, EO Cape Town, and similar groups.
- Show up with clear conversation frames: “diagnostic thinking”, “don’t build yet”, and “software as a growth lever”.
- Treat these as long-term relationship channels, not high-pressure pitch environments.
- Use the “boring content” strategy to repeat key messages from multiple angles, rather than chasing novelty.
- Turn LinkedIn posts into blogs, newsletters, and nurture sequences (e.g. “Jargon Decoder”, “Bullshit Translator”, “5 Red Flags”).
- Build a repeatable case-study factory that captures real language from clients and surfaces credible outcomes.
- Wire all of this into a simple monthly newsletter that keeps prospects and nurture contacts warm.
- Structure blogs and Resources pages with FAQ sections that answer the exact questions Gemini/ChatGPT surface.
- Optimise for “GEO”/LLM SEO so Polymorph appears in answer boxes for key queries (custom vs off-the-shelf, integration choices, dev agency red flags).
- Use case-study and decision-guide content (“When custom makes sense”, “Integrating SA gateways”) as LLM-friendly assets.
- Use targeted outbound email to a small, carefully chosen list of executives where Polymorph already has context.
- Limit LinkedIn DMs to warm-ish contexts (events, mutual connections, content interactions) — no automation, no spray-and-pray.
- Anchor all outbound around offering diagnostics and help, not pitching full builds.
- One recording day per month, two conversations per session, handled end-to-end by a studio partner.
- Focus on human, off-the-cuff conversations about products, decisions, and trade-offs — not just “custom software”.
- Repurpose episodes into shorts, clips, and written content that feeds LinkedIn, newsletter, and the site.
Designing Around the Steps That Already Perform Well
The funnel formalises what’s already happening: light discovery, a deeper diagnostic pitch, a paid concept design, then — only when it’s right — a longer partnership.
Phase-Based Execution With Clear Ownership — No Dates Yet
This is a phase plan, not a Gantt chart. Dates get added after buy-in; for now, the focus is on sequencing and ownership.
CRM tells the truth, offers are clearly packaged, and warm prospects stay warm.
Growth Engine pillars online in a test-first way — high-trust, low-noise channels first.
Double down on what works, fold in the retainer, decide on Polycast.