Skip to main content

BuildingPlanB Hub

Day 64 of Building Plan B

BuildingPlanB | Learning AI by building real product

Learning AI by building practical products in public.

I’m a working dad in Singapore rebuilding my product craft, one shipped product at a time.

No guru claims. Just real builds, real lessons, and staying adaptable.

Current mode: building 2 to 3 products in parallel, with a 6-in-90 target.

Profile illustration of a working dad in Singapore, half human and half machine.
A reminder to stay human, but build with systems: calm, repeatable, and resilient.

6 Products in 90 Days

This is the operating system for BuildingPlanB: six small, useful products in 90 days so I can hone my product craft with AI and learn AI through real shipping.

Operating rules

  • Every product must solve a real problem I understand
  • Keep each build small enough to ship while working full time
  • Run 2 to 3 products in parallel only when the learning compounds
  • Publish the lesson even when the week is messy

Progress

1/6

Current sprint: Apr to Jun 2026

Day 64

Live
1
Building
2
Queued
3
Live Building
See all product logs

Current Product Plan

The portfolio is intentionally narrow: one product is live, two are being built, and every product has to teach a reusable AI-building capability.

1 live · 2 building

  1. Live

    Runway Calculator

    Proof of useful AI-assisted shipping

    Goal

    Help working professionals answer a stressful question quickly: if income stops, how long can the household last?

    Learning objective

    Refine a repeatable AI development workflow across scoping, UI, export, analytics, and product hardening.

    Next milestone

    Keep improving the product from real usage signals while documenting what the AI workflow is good at and where it still needs human judgment.

  2. 2

    Building

    ClawBuddy (name TBC)

    Developer workflow product

    Goal

    Turn recurring OpenClaw friction into a practical companion for auth expiry, usage visibility, and reliable scheduled work.

    Learning objective

    Learn deeper AI setup patterns, including MCP, automations, and operational architecture I can reuse across future tools.

    Next milestone

    Validate the smallest version that saves real time in my own workflow before adding broader automation features.

    Build note coming soon

  3. 3

    Building

    LearnTogether (name TBC)

    Family-first creative product

    Goal

    Build a toddler learning game my daughter genuinely enjoys, with simple parent-child play and progress that feels encouraging.

    Learning objective

    Learn AI-first product design across gameplay, generated assets, accessibility, and a child-friendly feedback loop.

    Next milestone

    Keep the first playable loop small, readable, and fun enough to test at home before expanding the content set.

    Build note coming soon

Reflections from the build

I share what shipped and what I learned, in plain language for working professionals.

Long-form notes + short social summaries · Last updated: 1 May 2026

Day-by-day archive (19)
  • Day 19 · Week 3 · 17 Apr 2026

    What shipped: Rewrote Act 1–3 to sound more like me and ran multiple UX/design passes on the Story section, including a lighter Promise block with subtle delight animation and cleaner visual rhythm.

    Lesson learned: Good copy is not one-shot. The best version came from fast feedback loops, trimming repetition, and shaping tone until it actually sounded human.

  • Day 18 · Week 3 · 16 Apr 2026

    What shipped: Shipped Runway UX Pass 1 on a branch, then ran targeted audit/fix rounds (optional-field errors visibility, alignment and spacing cleanup, clearer copy hierarchy), and merged it to main after final checks.

    Lesson learned: Fast iteration works best when each feedback loop is specific: patch, verify, and ship instead of waiting for a perfect one-shot redesign.

  • Day 17 · Week 3 · 15 Apr 2026

    What shipped: Prototyped a Start Here (60s) onboarding section with clear first-click paths, reviewed the live preview, then intentionally parked it for later until the site has more depth.

    Lesson learned: Not every good idea should ship immediately. Timing matters — better to stage the right feature at the right maturity point.

  • Day 16 · Week 3 · 14 Apr 2026

    What shipped: Connected Runway Calculator to runway.buildingplanb.com, aligned canonical/share URLs, and shipped the initial downloadable PDF snapshot so users can keep a one-page runway health report.

    Lesson learned: Product trust compounds when distribution and utility ship together: one clear URL to access it, one concrete output people can keep.

  • Day 15 · Week 3 · 13 Apr 2026

    What shipped: Back on Runway Calculator and starting the PDF feature so users can download a one-page summary of their runway health.

    Lesson learned: A simple, useful output beats a bigger roadmap — start with one clear takeaway people can keep and act on.

  • Day 14 · Week 2 · 12 Apr 2026

    What shipped: Bought and configured the buildingplanb.com domain, set up routing in Vercel, and locked apex canonical so the public home now points to one stable URL.

    Lesson learned: Two weeks of behind-the-scenes work is only useful when I commit and ship the visible foundation — this was that lock-in moment.

  • Day 13 · Week 2 · 11 Apr 2026

    What shipped: No feature shipped today. I was still sick and low-energy, so I focused on rest and only handled essentials at home.

    Lesson learned: Full-time salary brings real stability during rough patches, which is exactly why I want a second income stream as extra security.

  • Day 12 · Week 2 · 10 Apr 2026

    What shipped: Recovery day again — no shipping, no sprinting, just dad duty and getting better.

    Lesson learned: Building in public includes down days too. Consistency means returning after setbacks, not pretending they do not happen.

  • Day 11 · Week 2 · 9 Apr 2026

    What shipped: Got hit by sickness and had to pause execution. No product work shipped; energy went to recovery and father duty.

    Lesson learned: Hard days make me appreciate having a full-time paycheck, and they reinforce why I’m building side income that does not depend on one source.

  • Day 10 · Week 2 · 8 Apr 2026

    What shipped: No feature shipped yesterday — I was sick while still on father duty, so I focused on recovery and kept momentum by documenting the day honestly.

    Lesson learned: Hard days make me appreciate full-time pay, and they also remind me why I’m building side income so my family is less dependent on a single paycheck.

  • Day 9 · Week 2 · 6 Apr 2026

    What shipped: Shipped B-lite daily journal pages with shareable URLs, linked Build Log day entries to each page, and added per-day metadata plus OG image generation for better social previews and SEO foundation.

    Lesson learned: Lightweight daily entries can still compound into strong distribution and discoverability when each day has its own structured page.

  • Day 8 · Week 2 · 4 Apr 2026

    What shipped: Automated site freshness signals (Day badge + Last updated), refined hero/build-log clarity, completed two audit/fix passes for UX readability, and merged the full update to production.

    Lesson learned: Trust increases when progress is automatically reflected and UX quality is tightened before publish.

  • Day 7 · Week 1 · 3 Apr 2026

    What shipped: Refined my build workflow: OpenClaw for quick-win features and Codex for deeper, more complex tasks that need focused execution.

    Lesson learned: Speed comes from picking the right tool for the depth of work.

  • Day 6 · Week 1 · 2 Apr 2026

    What shipped: Launched BuildingPlanB Hub and locked next improvements: real links, clearer mission block, Start Here section, update/day tracking, and social preview metadata.

    Lesson learned: Shipping gives me control back.

  • Day 5 · Week 1 · 1 Apr 2026

    What shipped: Posted on all 3 platforms and published a short reel.

    Lesson learned: Consistency matters most when audience is small.

  • Day 4 · Week 1 · 31 Mar 2026

    What shipped: Clarified the story: working dad in Singapore, building after office hours, no fake guru vibe.

    Lesson learned: Honest positioning makes execution easier.

  • Day 3 · Week 1 · 30 Mar 2026

    What shipped: Scoped Runway Calculator to answer: "If income stops, how long can we last?"

    Lesson learned: Simple + useful wins.

  • Day 2 · Week 1 · 29 Mar 2026

    What shipped: Locked rules: one project, launch before perfect, no zero days.

    Lesson learned: Discipline beats motivation.

  • Day 1 · Week 1 · 28 Mar 2026

    What shipped: Stopped doom-scrolling, started building in public, and set a $10k/month side-income target.

    Lesson learned: Fear drops when there is a plan.

Story / Why this exists

This is my safety net, built one night at a time.

When layoffs started hitting teams around me, I realized one uncomfortable truth: hope is not a strategy. I needed a second track that I could control.

  1. Act 1

    The wake-up call got personal

    Layoffs became real when people around me got hit.

    • As a dad in Singapore, I can’t leave my family’s stability to one paycheck.
  2. Act 2

    Build, Learn, Repeat

    With AI, I finally feel this is possible.

    • I use small pockets of time after work, after my kid sleeps, and on weekends to build practical tools and learn by doing.
  3. Act 3

    Public accountability, real progress

    I keep this build log in public to stay honest.

    • I log wins and failures so I learn each round and stop restarting from Day 1.

The Promise

No zero day
Build before emergency, not after.

No zero day: each week I ship something, post something, or learn something useful.

ShipPostLearn