How Summit repositioned from forecasting tool to low-code calculator platform

Executive overview

Summit built a powerful "whiteboard that does math" but found only a small fraction of users could complete the builder, leaving the majority stranded without access to the outputs they actually wanted. The solution was a repositioning around calculators — a recognisable artifact — combined with a publish-and-embed layer that separates makers from users.

The core insight: if your output isn't a thing people recognise, you're not just fighting a product problem — you're fighting a category problem.

Why the original positioning failed

• "Whiteboard that does math" resonated with some but required users to invent a mental model from scratch
• ~90% of trial users couldn't complete the builder or didn't know what to do with the result
• The 10% who latched on loved it — but that's too narrow a funnel for growth
• Users still had the underlying problems (forecasting, pricing, runway) — they just couldn't self-serve the tool

The repositioning to calculators

• "Calculator" is diminutive but immediately legible — users wake up knowing they want one
• April Dunford's framing applies: the right word gives just enough grip on what you are and aren't
• Posting "does anyone want a calculator?" in a Slack community generated ~13 responses in 24 hours — strong signal
• Makers also need a word their audiences understand; "calculator" works for both sides
• The decision mirrors Rob Walling's own experience accepting "marketing automation" for Drip despite disliking the term

The role of the design agency in forcing clarity

• Hired a strategic design agency to rebuild the marketing site — rare combination of design skill and strategic thinking
• Agency pushed the team to map a before-and-after day-in-the-life for a prospect
• The project took 6–8 weeks instead of 4, because positioning had to be resolved first
• 75% of Matt's mental energy during that period went to language and positioning, not product
• Lesson: finalise positioning before commissioning a new site, not during

Adding the publish and embed layer

• Summit added a publish button and WYSIWYG interface so builders could share calculators publicly
• Embedded calculators carry a "powered by Summit" sponsor link (free tier) or can be white-labelled (paid)
• Example: a mastermind operator embedded a sales payback calculator into their member portal with no building required
• SaaS metrics content sites are embedding calculators in blog posts to illustrate retention and acquisition concepts
• Highest-ever traffic week recorded post-relaunch; best revenue growth month to date

Building a two-sided marketplace as a bootstrapped-ish company

• Summit has raised some funding, giving more runway than a pure bootstrap
• Key advantage: Summit can supply the calculator library itself, so it doesn't need to cold-start both sides simultaneously
• The maker-to-user ratio is highly asymmetric — one builder can create calculators used by thousands
• Analogy: Nintendo publishing first-party games to prove the platform before third-party developers arrive
• Priority now is proving demand (usage, embeds, traffic) so developers are motivated to contribute supply
• Avoid scaling headcount before validating positioning — large teams create expensive content debt when repositioning

Signals post-relaunch

• Traffic floor is now higher than any previous launch spike
• Revenue growth plateau broken — best month to date
• Builders reaching out asking to publish their own calculators for their audiences
• Churn roughly unchanged — growth is coming from new demand, not retention improvement