Product Development

When you open this playbook in the Profit System, you will find:

• Action 1: Innovation Pipeline

  Map out your 12-24 month product roadmap with clear timelines, resource allocation, and strategic rationale for each initiative. Separate core improvements from new experiments.

  Show full action →

  Hide full action

  What to Do

  Map your 12-24 month product roadmap with clear timelines, resource requirements, and strategic rationale for each item. Separate core product improvements from new experiments so you can invest in both without confusing the two. This gives you a structured plan for what to build, when to build it, and why it matters.

  Why It Matters

  Most small businesses either never innovate (they sell the same thing for years until it stops working) or they innovate chaotically (chasing every new idea without finishing anything). Both paths lead to stagnation. A structured pipeline solves this by giving innovation a container. You know what you are working on now, what is coming next, and what is just an idea being tested. Without this structure, the loudest idea wins - usually whatever the owner got excited about last Tuesday.

  How to Use This

  Build your pipeline in three stages: gather all ideas, categorise them, then sequence them into a timeline.

  ---

  Gather Your Product Ideas

  • [ ] Brain-dump every product idea, improvement, and enhancement you have been thinking about - New offers, add-ons, upgrades, bundled packages, digital products, events, service improvements. Get everything out of your head and onto paper.
  • [ ] Review customer feedback from the last 6 months - What have customers asked for? What have they complained about? What do they wish you offered?
  • [ ] ⚡ Quick Win: Check your last 10 support tickets or complaint emails. The product improvements hiding in complaints are usually the most valuable ones.
  • [ ] Ask your team: "If you could fix or add one thing to what we offer, what would it be?" - Front-line staff see problems the owner misses.
  • [ ] Review competitor offerings - What are competitors offering that you do not? Not to copy, but to spot gaps and opportunities.

  Categorise Each Idea

  • [ ] Label each idea as one of three types:
    • Core improvement - Makes your existing offer better (faster delivery, higher quality, better experience)
    • Extension - Adds something new to your existing offer (upsell, add-on, new tier)
    • Experiment - Completely new offer or market (untested, higher risk, higher potential reward)
  • [ ] Score each idea on three dimensions (1-5 each):
    • Revenue potential - How much could this generate?
    • Customer impact - How much would customers value this?
    • Effort required - How much time, money, and resource to build?
  • [ ] Calculate priority: (Revenue + Customer Impact) minus Effort - Higher scores go higher on the list.
  • [ ] Apply the 70/20/10 rule as a guideline - 70% of resource on core improvements, 20% on extensions, 10% on experiments. Adjust to fit your business, but the principle holds: protect your core while testing the future.

  Build Your Timeline

  • [ ] Place your top-priority core improvements in the next 0-6 months - These protect your existing revenue and keep current customers happy.
  • [ ] Place extensions in the 6-12 month window - These grow revenue from your existing base once the core is solid.
  • [ ] Place experiments in the 12-24 month window - These explore new territory. Some will fail. That is the point.
  • [ ] For each item in the next 6 months, define: owner, deadline, resources needed, and success metric - Vague items on a roadmap are wishes, not plans.
  • [ ] Set quarterly review points - The pipeline is a living document. Review it every quarter and reprioritise based on what you have learned.

  ---

  Expected Outcome

  • A complete inventory of all product ideas, improvements, and innovations
  • Each idea categorised as core improvement, extension, or experiment
  • A prioritised 12-24 month roadmap with clear sequencing
  • The next 6 months planned in detail with owners and deadlines
  • A quarterly review rhythm to keep the pipeline current

  Coach Notes

  The most common mistake is filling the pipeline with experiments while ignoring core improvements. Exciting new ideas are more fun than fixing what already exists. But core improvements protect revenue and often deliver the biggest return for the least effort. Push clients to strengthen the core first.

  Watch for pipelines that are really just wish lists. Every item needs a "why now" and a "what does success look like." If a client cannot answer those questions, the idea is not ready for the pipeline.

  If a client has never mapped a product roadmap before, start with just the next 6 months. A 24-month roadmap can feel overwhelming for someone who has been making product decisions on instinct. Build the muscle first, extend the timeframe later.

• Action 2: Demand Validation Framework

  Test customer demand before building anything. Use pre-orders, landing pages, customer interviews, and pilot programmes to validate need and willingness to pay.

  Show full action →

  Hide full action

  What to Do

  Test customer demand before building anything. Use pre-orders, landing pages, customer interviews, pilot programmes, and other low-cost methods to validate that people actually want what you plan to create and are willing to pay for it. This prevents the most expensive mistake in business: building something nobody buys.

  Why It Matters

  The graveyard of small business is full of products that the owner loved but customers did not want. Building first and selling later is backwards. Every week you spend developing an unvalidated product is a week of revenue you will never get back. Eric Ries' Lean Startup principle applies to every business, not just tech startups: build the minimum version, test it with real customers, and iterate based on real data. The goal is to fail cheaply and learn fast, not to perfect something in isolation and hope the market agrees.

  How to Use This

  Pick the validation method that fits your product idea, run the test, and use the results to decide whether to build, adjust, or abandon.

  ---

  Choose Your Validation Method

  • [ ] Customer conversations (lowest effort, highest insight) - Talk to 5-10 ideal customers about the problem your product solves. Do not pitch your solution. Ask about their pain, what they have tried, and what they would pay for a fix. If the problem is not urgent for them, the product will not sell.
  • [ ] ⚡ Quick Win: Send a one-question survey to your existing customer list: "If we offered [product concept in one sentence], would you be interested? Reply yes or no." Simple data, zero cost.
  • [ ] Landing page test - Build a simple page describing the offer with a "register interest" or "join waitlist" button. Drive traffic to it and measure sign-up rate. No product needed.
  • [ ] Pre-order or pre-sale - Offer the product at a discount before it exists. Real money committed is the strongest validation signal. If people will not pay in advance, they probably will not pay later either.
  • [ ] Pilot programme - Deliver a stripped-down version to 3-5 customers at a reduced price in exchange for detailed feedback. You learn what works, what does not, and what customers actually value before building the full version.
  • [ ] Competitor analysis - If a competitor already sells something similar and is growing, demand is partially validated. Your job becomes differentiation, not demand creation.

  Design Your Test

  • [ ] Define your hypothesis in one sentence - "I believe [target customer] will pay [price] for [product] because [reason]." Write it down. You need to know what you are testing.
  • [ ] Set your success threshold before you start - What number or result would make you confident enough to build? 10 pre-orders? 50 waitlist sign-ups? 8 out of 10 interviewees saying they would buy? Define "pass" and "fail" in advance so you cannot move the goalposts.
  • [ ] Set a time limit - Give the test 2-4 weeks. Long enough to get meaningful data, short enough that you do not lose momentum.
  • [ ] Identify your test audience - Who specifically will you test with? Existing customers, email list, social media followers, cold prospects? The audience affects the results.
  • [ ] Budget your test - Most validation tests cost very little. Landing pages, email surveys, and conversations are nearly free. Pre-orders require some marketing spend. Set a budget and stick to it.

  Evaluate Results and Decide

  • [ ] Compare results to your pre-set threshold - Did you pass or fail? Be honest. Wishful thinking at this stage is expensive later.
  • [ ] Look for patterns in the feedback - What did customers love? What concerned them? What would they change? This shapes the final product.
  • [ ] Make one of three decisions:
    • Build - Demand is validated, move to development
    • Adjust - Interest exists but the offer needs changes before building
    • Abandon - Demand is not there, move on to the next idea without guilt
  • [ ] Document what you learned - Even failed tests produce valuable insight. Write down what you discovered about customer preferences, pricing sensitivity, or market gaps. This feeds your next innovation.

  ---

  Expected Outcome

  • A clear validation method chosen and executed for your product idea
  • Real data from real customers, not assumptions
  • A confident build/adjust/abandon decision backed by evidence
  • Documented learnings that improve your next product decision
  • Reduced risk of investing time and money in products that will not sell

  Coach Notes

  The biggest barrier is emotional attachment. Clients fall in love with their product idea and treat validation as a formality rather than a genuine test. Push them to define success criteria before running the test, and hold them to those criteria when results come in.

  Watch for "false validation" - asking friends and family who say "great idea!" but would never actually buy. Real validation involves people in the target market making a commitment, ideally financial. Compliments are not validation. Purchases are.

  If a client is reluctant to test because "it will take too long," reframe it: building an unvalidated product takes 3-6 months. A validation test takes 2-4 weeks. Which is the bigger waste of time if the idea is wrong?

• Action 3: Portfolio Balance Review

  Analyse how much time and resource you allocate to core offers vs experimental ones. Set clear criteria for what percentage should go where based on your market position and growth goals.

  Show full action →

  Hide full action

  What to Do

  Analyse how your time, money, and team resource is allocated between your core offers and any experimental or new products. Set clear criteria for what percentage of resource goes where, and make deliberate decisions about your product portfolio rather than letting it drift.

  Why It Matters

  Left unmanaged, product portfolios become bloated. Every new idea gets a "yes," nothing gets retired, and the team ends up supporting six offers when they only have capacity for three. The result is mediocre delivery across the board. Your best products suffer because resource is being drained by marginal ones. A portfolio review forces the hard conversations: what should we stop offering? What deserves more investment? What looked promising but is not pulling its weight?

  How to Use This

  List everything you sell, measure its performance, and rebalance your portfolio around what is actually working.

  ---

  Inventory Your Current Portfolio

  • [ ] List every product or service you currently offer - Include every tier, package, add-on, and variant. If a customer can buy it, it goes on the list.
  • [ ] ⚡ Quick Win: Count the items on your list. If you have more than 5-7 distinct offers, you are almost certainly spread too thin. Most small businesses perform best with 2-4 core offers.
  • [ ] For each offer, record:
    • Revenue generated in the last 12 months
    • Gross margin (revenue minus direct delivery costs)
    • Number of active customers
    • Time spent delivering and supporting it (hours per month)
    • Age of the offer (how long have you been selling it?)

  Analyse Performance

  • [ ] Calculate revenue per hour for each offer - Total revenue divided by total hours spent. This reveals which offers are worth your time and which are deceptively busy.
  • [ ] Rank offers by gross margin percentage - Which offers keep the most money after delivery costs?
  • [ ] Identify your "hero" products - The 1-2 offers that generate the majority of your revenue and profit. These deserve the most protection and investment.
  • [ ] Identify your "zombie" products - Offers that still exist but barely generate revenue, consume disproportionate effort, or have not grown in over a year. These are candidates for retirement.
  • [ ] Identify your "rising stars" - Newer offers showing growth in revenue or customer interest, even if still small. These may deserve more investment.

  Rebalance Your Portfolio

  • [ ] Set your target allocation - What percentage of your team's time and your budget should go to: hero products (protect and optimise), rising stars (invest and grow), and experiments (test and learn)?
  • [ ] Compare target vs. reality - Where is the gap? Most businesses over-invest in zombies and under-invest in heroes.
  • [ ] Decide the fate of each zombie product - For each underperformer, choose: sunset it (stop selling), simplify it (reduce the resource it consumes), or set a 90-day deadline for improvement.
  • [ ] Reallocate freed-up resource - Every hour or pound saved from retiring a zombie should go to a hero or rising star. Be specific about where it goes.
  • [ ] Set a 6-month review date - Portfolio balance is not a one-time exercise. Markets change, offers mature, new opportunities emerge. Review every 6 months.

  ---

  Expected Outcome

  • A complete inventory of every product and service with performance data
  • Hero, zombie, and rising star products clearly identified
  • Underperforming offers retired or given a clear improvement deadline
  • Resource reallocated from low-performers to high-performers
  • A target allocation set for ongoing portfolio management

  Coach Notes

  Retiring a product is emotionally difficult for owners. They built it, they remember the first customer who loved it, and stopping feels like failure. Reframe it: retiring a product that no longer serves you is not failure. It is good management. The resource you free up goes to something better.

  Watch for the "but what if someone asks for it" trap. Clients keep zombie products alive because one customer per quarter might want it. Calculate what that one sale actually costs in terms of ongoing support, complexity, and distraction. It is almost never worth it.

  If a client has never done a portfolio review, the first one will be revealing. Most owners have no idea how much time each offer actually consumes. The data often triggers immediate decisions to simplify.

• Action 4: Product Iteration System

  Build a repeatable process for gathering customer feedback, prioritising improvements, and rolling out updates. Make sure your best products keep getting better.

  Show full action →

  Hide full action

  What to Do

  Build a repeatable process for gathering customer feedback, prioritising improvements, and rolling out updates to your products and services. Instead of improving things when you feel like it or when something breaks, create a rhythm that ensures your offers get better every quarter.

  Why It Matters

  Products that do not improve die slowly. Your customers' expectations rise every year, competitors copy your best ideas, and the market moves on. But most small businesses only improve their products reactively - when a customer complains, when a competitor launches something new, or when the owner has a random burst of inspiration. A systematic iteration process means improvements happen regularly, are based on real feedback, and get implemented without chaos.

  How to Use This

  Set up three things: a feedback collection system, a prioritisation method, and a release rhythm. Then run the cycle continuously.

  ---

  Build Your Feedback Collection

  • [ ] Choose 3 feedback channels and set them up:
    • Post-purchase or post-delivery survey (keep it to 3-5 questions maximum)
    • Quarterly check-in conversation with top clients (phone or video, not email)
    • Internal team debrief after each project or delivery cycle
  • [ ] ⚡ Quick Win: Add one question to your next client interaction: "What is one thing we could do better?" This costs nothing and the answers are gold.
  • [ ] Create a central feedback log - A simple spreadsheet or document where all feedback goes, regardless of source. Columns: Date, Source, Feedback, Product/Service, Frequency (how often you hear this), Priority.
  • [ ] Assign someone to review the log monthly - Feedback that sits unread is worse than no feedback at all. Someone needs to own this.
  • [ ] Track feature requests separately from complaints - Complaints tell you what is broken. Requests tell you what is missing. Both matter but they need different responses.

  Prioritise Improvements

  • [ ] Review your feedback log at the start of each quarter - Look for patterns. What feedback appears most frequently? What comes from your best customers?
  • [ ] Score each potential improvement on three criteria:
    • Customer impact (how many customers benefit and how much?)
    • Revenue impact (will this help retain customers, increase prices, or attract new ones?)
    • Implementation effort (how much time and money to build?)
  • [ ] Apply the "quick wins first" principle - High impact, low effort improvements go first. Always. Saving the easy wins for later while tackling hard ones first is a common trap.
  • [ ] Select 2-3 improvements per quarter - No more. Fewer improvements done well beats a long list done poorly.
  • [ ] Write a one-sentence brief for each selected improvement - What changes, why, and what does success look like? Keep it simple enough that anyone on the team can understand.

  Implement and Release

  • [ ] Assign an owner for each improvement - One person responsible for making it happen, even if multiple people contribute.
  • [ ] Set a deadline within the quarter - If an improvement cannot be done in a quarter, break it into smaller pieces. Shipping partial progress beats planning indefinitely.
  • [ ] Communicate changes to customers - When you improve something, tell people. An email, a note in a meeting, a social post. Customers notice when things get better, but they appreciate you pointing it out.
  • [ ] Measure the impact - After implementation, check: did customer satisfaction improve? Did complaints on that topic decrease? Did retention or revenue change? If you cannot measure it, at least gather anecdotal feedback.
  • [ ] Start the cycle again - Review the feedback log, pick the next improvements, implement, measure. This never stops.

  ---

  Expected Outcome

  • A working feedback collection system with multiple channels
  • A central log where all customer feedback is captured and reviewed
  • A quarterly rhythm for selecting and implementing product improvements
  • Clear ownership and deadlines for each improvement
  • A continuous cycle that ensures your products get better every quarter

  Coach Notes

  The biggest risk with this action is over-engineering. Clients hear "system" and think they need software, dashboards, and complex workflows. Push back. A spreadsheet and a quarterly calendar is enough for most small businesses. The system should take minutes to maintain, not hours.

  Watch for clients who collect feedback but never act on it. That is worse than not collecting it, because customers feel ignored. If you ask for feedback, you must close the loop. Even if the answer is "we heard you and we are not changing this right now because X."

  Help clients distinguish between feedback that represents real patterns and feedback from one loud customer. A single request is an anecdote. The same request from five different customers is a signal. Teach them to look for frequency before acting.