Squarely Puzzles — Growth Strategy

A practical playbook for moving Squarely from lumpy, network-driven revenue to sustainable, compounding growth. Built on the Racecar Growth Framework, growth loops thinking, and the Four Fits Framework.

1. Current State

Products:

• Puzzle books published on KDP (Amazon) — the only revenue-generating product today
• iOS app in development — not yet launched
• Two additional invented games — not yet published

Revenue: A few thousand dollars, lumpy and network-driven. Most sales come from personal network, not organic discovery. This is classic pre-engine territory per the Racecar Framework — the business runs on turbo boosts (personal pushes, social posts) rather than a self-sustaining engine.

Distribution: Amazon/KDP is the only channel. No paid acquisition, no content marketing, no systematic social presence, no email list for direct audience ownership.

Team: Two people — the founder and his dad. As noted in SC 019, two people filling eight organizational seats, with marketing as the biggest capability gap.

Strategic context: Squarely doubles as a proving ground for Ray Data Co’s data capabilities (01-projects/squarely-puzzles/index) and content fodder for the newsletter (SC 018).

2. Racecar Diagnosis

Using the Racecar Framework, here is where Squarely’s growth initiatives sit today and where they should sit.

Engine (what drives sustained growth)

Current engine: Amazon Search/Browse (Content Engine) Amazon’s algorithm surfaces books to buyers searching for puzzle content. This is a content engine where each new book adds fuel. The loop: publish book -> Amazon indexes it -> searchers find it -> sales generate reviews and ranking signals -> more visibility -> more sales.

This engine exists but is barely spinning. Likely reasons: thin catalog (limited fuel), weak listing optimization (lubricant issue), and no external traffic driving Amazon ranking signals.

Potential engine: Viral/Casual Contact (iOS app) If the iOS app lets players share puzzle results or challenge friends, there’s a potential casual contact viral loop. The loop: player completes puzzle -> shares result/challenge -> friend sees it -> downloads app -> completes puzzle -> shares. This loop has a naturally low branching factor, so it needs high volume to matter.

Turbo Boosts (one-off spikes)

This is where most current growth comes from, and that’s the problem. Personal network sales, social media pushes, newsletter features — all turbo boosts. They provide activation energy but don’t compound.

Useful turbo boosts to deploy intentionally:

• iOS app launch event (PR, social, newsletter)
• New book launches
• Holiday/seasonal gift pushes
• Cross-promotion via the Sanity Check newsletter

The key per the Racecar Framework: don’t mistake these for the engine. Use them to kickstart the engine, then let the engine take over.

Lubricants (conversion/activation/retention optimizations)

These only matter once an engine is running. Premature optimization is the third pitfall in the framework. That said, some lubricants are table stakes:

• KDP listings: Cover design, description copy, A+ content, keyword optimization — these are conversion lubricants on the Amazon search engine
• App onboarding: Setup -> aha -> habit path (covered in Section 5)
• Review generation: Post-purchase prompts to leave Amazon reviews — retention lubricant that feeds the engine

Fuel

The Amazon content engine needs more puzzle content (more books, more variety). The viral engine needs users as fuel. Per the framework, fuel type determines pricing strategy — content fuel means the production pipeline is the bottleneck, not capital.

Diagnosis summary: Squarely is in Pitfall #2 — mistaking turbo boosts for an engine. The Amazon content engine exists but is underfueled and under-lubricated. The priority is to fuel and optimize that engine before layering on new ones.

3. Growth Loop Analysis

Per Growth Loops Are the New Funnels and Acquisition Loops, here are the loops available to Squarely, assessed for feasibility.

Loop 1: Amazon Content Loop (Primary — KDP)

Type: Content loop (company-generated) Mechanics: Publish puzzle book -> Amazon indexes and surfaces to searchers -> buyer purchases -> reviews/sales velocity improve ranking -> more visibility -> more purchases. Revenue reinvested into more book production. Feasibility: HIGH. This is the most natural loop for KDP. The constraint is fuel (content production) and lubricant (listing quality). The loop already exists in embryonic form. Key metrics: Sales per book per month, organic search impressions, review count, BSR (Best Seller Rank). Ceiling: Medium. Puzzle books are a niche within a niche. Saturation will come, but we’re nowhere near it.

Loop 2: Word of Mouth (Both KDP and iOS)

Type: Viral loop (organic) Mechanics: Player enjoys puzzle -> tells friend/family -> friend buys/downloads -> enjoys puzzle -> tells others. Feasibility: MEDIUM. Puzzles naturally generate word of mouth (people talk about things they do for fun). But the branching factor is low and time-to-conversion is long. This won’t be a primary engine but it compounds slowly alongside other loops. Key lever: Make the puzzle experience distinctive enough that people mention it. The “Squarely” format is novel — lean into that.

Loop 3: Casual Contact Viral Loop (iOS app)

Type: Viral loop (casual contact) Mechanics: Player completes puzzle -> app generates shareable result image (think Wordle) -> posted to social/texted to friend -> non-player sees brand -> repeated exposure builds familiarity -> eventual download. Feasibility: MEDIUM-HIGH if designed correctly. Wordle proved this loop works for puzzle games. Three requirements from the framework: (1) high branching factor — social sharing can achieve this, (2) patience — casual contact loops are slow, (3) measure the ripple effect, not just direct clicks. Critical design decision: The share format must be compelling on its own (not just “I scored X”). Wordle’s colored grid was genius because it was visually interesting and spoiler-free.

Loop 4: Paid Loop (KDP — Amazon Ads)

Type: Paid acquisition Mechanics: Revenue from book sales -> reinvest in Amazon Sponsored Product ads -> ads drive more sales -> revenue grows -> reinvest more. Feasibility: LOW-MEDIUM right now. Per the acquisition loops framework, paid loops need capital and a known LTV:CAC ratio. At current revenue (“a few thousand”), the capital pool is tiny. However, Amazon ads for KDP can be very efficient at small scale because targeting is intent-based (people actively searching for puzzles). Worth testing with a small budget to learn unit economics. Risk: Per the framework, strong paid acquisition can mask poor retention. Don’t scale paid until the organic engine is healthy.

Loop 5: Content Marketing Loop (Cross-platform)

Type: Content loop (company-generated) Mechanics: Create puzzle-related content (social posts, short videos, blog) -> content attracts puzzle enthusiasts -> they discover Squarely -> some buy/download -> content performance data informs next content. Feasibility: LOW for now. This is a real loop but it requires consistent content production, which is a resource constraint for a two-person team. The newsletter already serves as a content engine for Ray Data Co broadly (SC 018), but Squarely-specific content marketing is a separate investment. Exception: Short-form video (TikTok/Reels) of puzzle-solving could work with minimal production effort. The puzzle format is inherently visual.

4. Four Fits Assessment

Applying the Four Fits Framework and Model/Channel Fit to both product lines.

KDP Puzzle Books

KDP verdict: The four fits are aligned. The bottleneck is not fit — it’s fuel (catalog depth) and lubricant (listing optimization).

iOS App (Planned)

iOS verdict: The fits are not yet locked. The critical decisions are (1) daily vs. occasional use frequency, and (2) free-with-ads vs. freemium monetization model. These two choices cascade through every other fit.

Recommendation for iOS: Design for daily use (daily puzzle challenge) with a freemium model (free daily puzzle, paid puzzle packs or ad removal). This combination maximizes viral potential per model/channel fit and keeps the product in the Habit Zone per the engagement framework.

5. Activation Path

Using Reforge’s activation chain, designed backward from habit moment.

KDP Puzzle Books

Habit Moment: Buyer has completed 3+ puzzles and returned to the book multiple times within the first week. They’re hooked. Aha Moment: Buyer completes their first Squarely puzzle and “gets” the format. The novel mechanic clicks — this isn’t just another crossword or sudoku. Setup Moment: Buyer has the book, opened it, and read the brief instructions. Minimal friction here — physical products have natural setup.

Levers:

• The instructions page must be crystal clear — if the format is novel, a confused buyer never reaches aha
• Include an easy “starter” puzzle on the first page to accelerate aha
• Back-of-book CTA to buy the next book or download the app (feeds the loop)

iOS App

Habit Moment: Player has completed puzzles on 3+ separate days within first 10 days. They’re forming a daily habit. Per retention measurement, this should be the metric: “completed a puzzle” (not “opened the app”) at daily frequency. Aha Moment: Player completes their first puzzle and sees the satisfying completion screen. They understand the format and want another. Per the engagement framework, the aha needs: core action (complete puzzle), warm start (guided first puzzle), supporting actions (choose difficulty), and no empty states. Setup Moment: Player has downloaded the app, chosen initial preferences (difficulty level, puzzle type), and been presented with their first puzzle. Keep this to under 30 seconds.

Engagement loop design (per the engagement framework):

• Organic trigger: Boredom, break time, waiting — high-frequency triggers
• Action: Solve today’s puzzle
• Reward: Completion satisfaction (intrinsic), streak counter (intrinsic), shareable result (social)
• Manufactured triggers: Daily push notification (“Today’s puzzle is ready”), streak-at-risk notification (“Don’t break your 7-day streak!”)

Retention target: Per the retention framework, aim for a flat retention curve — not trending to zero. Casual puzzle games typically retain 10-20% at D30. If the curve flattens there, stacking cohorts produces growth even without increasing acquisition. If the curve trends to zero, fix retention before spending on acquisition.

6. Recommended Strategy

Ordered by priority. Do these in sequence, not in parallel — a two-person team can’t run multiple workstreams.

Phase 1: Fuel and Lubricate the Amazon Engine (Now - Month 2)

The Amazon content loop is the most viable engine today. It’s aligned on all four fits. It just needs fuel and lubrication.

Actions:

1. Expand the catalog. Publish the two unpublished games as KDP books. Each new book is fuel for the content engine. Target: 2 new titles within 60 days.
2. Optimize existing listings. Audit and improve every listing — cover design, description copy, backend keywords, A+ content if enrolled in Brand Registry. These are conversion lubricants per the Racecar Framework.
3. Start a review generation system. Include a polite review request in each book (back page). Reviews are the lubricant that accelerates the Amazon ranking flywheel.
4. Test Amazon Ads at $5-10/day. Small-budget Sponsored Product campaigns to learn unit economics. Target high-intent keywords (“puzzle books for adults,” category-specific terms). This tests whether a paid loop is viable alongside the organic content engine.

Success metric: Monthly revenue doubles from baseline within 60 days. If it doesn’t, the issue is product/market fit, not distribution.

Phase 2: Design the iOS App for Growth (Month 2 - Month 4)

Don’t just build an app. Design it as a growth engine from day one, using the frameworks above.

Actions:

1. Commit to daily puzzle format. This keeps the product in the Habit Zone and unlocks manufactured engagement loops.
2. Choose freemium model. Free daily puzzle + paid puzzle packs (or ad removal). Low friction enables viral channels per model/channel fit.
3. Build the share mechanic before anything else. The Wordle-style shareable result is the core of Loop 3 (casual contact viral). Design the share image to be: visually distinctive, spoiler-free, and branded with “Squarely” prominently. This is the engine — everything else is lubricant.
4. Implement the activation chain. Under-30-second setup, guided first puzzle, satisfying completion screen, streak system, daily push notification permission prompt (after first completed puzzle, not before).
5. Cross-link KDP and app. Include app download QR code in every book. Include “get the book” link in the app. Each product feeds the other.

Success metric: Retention curve analysis at D7/D14/D30 once launched. Target: curve flattening, not trending to zero.

Phase 3: Launch with Intentional Turbo Boosts (Month 4 - Month 5)

Use turbo boosts for their intended purpose: activation energy to spin up the viral engine.

Actions:

1. Coordinate launch across channels. Newsletter feature (01-projects/newsletter/index), social media blitz, friends-and-family push, Product Hunt or relevant indie game communities.
2. Seed the viral loop. Get 50-100 initial daily active players. Their shares seed the casual contact viral loop. Per the casual contact framework, multiple exposures are needed before conversion — so volume matters early.
3. Track the ripple effect. Don’t just measure direct shares-to-downloads. Watch for branded search increases, App Store browse traffic, and organic installs that correlate with sharing activity.

Success metric: Organic installs growing week-over-week without increasing turbo boost spend. That’s the signal the engine is catching.

Phase 4: Optimize and Expand (Month 5+)

Only after the engines are running:

1. A/B test share formats to maximize viral coefficient
2. Add social features (leaderboards, friend challenges) to increase branching factor
3. Launch the additional invented games as both KDP titles and app content
4. Consider a “Squarely” umbrella brand across the games portfolio
5. Build the data pipeline — this becomes the Ray Data Co case study (01-projects/squarely-puzzles/index)

7. Open Questions

These need founder input to refine the strategy:

1. Production capacity: How fast can the dad produce new puzzle content? This determines the fuel rate for the Amazon engine and the daily puzzle cadence for the app. Is content production the actual bottleneck?

2. iOS app timeline and scope: What’s the realistic ship date? Is the MVP scoped for daily puzzles + sharing, or something different? The growth strategy depends heavily on what the v1 includes.

3. Budget for Amazon Ads: Is there $150-300/month available to test paid loops on KDP? Even small-budget testing gives critical data on unit economics.

4. Revenue goal: What does “success” look like for Squarely in 12 months? $10K/year? $50K? $100K? This determines how aggressively to invest and whether the model/market math works per the monetization framework.

5. Daily puzzle format: Does the puzzle type lend itself to a daily challenge format, or is it inherently longer-form? This is the single biggest variable for the iOS app’s growth potential — it determines Habit Zone vs. Forgettable Zone per the engagement framework.

6. Existing data: Do we have any sales data, Amazon search term reports, or customer feedback to analyze? Even rough numbers would sharpen every recommendation above.

7. Willingness to cross-promote: How much is the founder willing to leverage the Sanity Check newsletter audience for Squarely? It’s a natural turbo boost but might dilute newsletter positioning.

8. Competitive landscape: What do the top-selling puzzle books on Amazon look like? What are the top puzzle apps doing with daily mechanics and sharing? A quick competitive audit would calibrate expectations for retention benchmarks and viral coefficients.