B2B SaaS Startup Building

Build an early business software company on solid ground: account model, billing, onboarding, honest MRR reporting, account health, churn and renewals, and the security and admin features that teams expect.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Then open the Marketplace in the app, search for B2B SaaS Startup Building, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🚀 Founding & Startups

B2B SaaS Startup Building

Building an early business software company, from first paying teams and onboarding to recurring revenue and early churn.

  1. Buyer, admin and end-user map for the product
  2. Workspace, seat and account data model
  3. Subscription billing set-up with a billing provider
  4. MRR and ARR definitions written down
  5. Privacy policy, DPA and sub-processor list
  6. Terms of service and subscription agreement
  7. Account-level product analytics events
  8. Help centre and support inbox first version
  9. Time to first value baseline for new teams
  10. Monthly SaaS metrics close
  11. Weekly account health review
  12. New account onboarding checklist
  13. Cancellation and churn reason log
  14. Renewal calendar for annual contracts
  15. Daily support triage and response times
  16. Feature request log linked to accounts
  17. Weekly changelog and release notes
  18. Failed payment recovery and dunning
  19. Uptime, incidents and status page
  20. Quarterly business reviews with top accounts
  21. Reading net and gross revenue retention
  22. Running a customer onboarding call
  23. Writing help articles that cut tickets
  24. Product-led versus sales-led motion study
  25. Enterprise security review and SOC 2 basics
  26. Cohort retention by signup month
  27. Interviewing customers who cancelled
  28. Free trial, freemium or demo-only decision
  29. Annual versus monthly billing terms
  30. Plan limits and feature gating in the product
  31. Single sign-on and role-based permissions
  32. Admin console for account owners
  33. Choosing the first three integrations
  34. Public API and webhooks first version
  35. Cutting time to first value in onboarding
  36. In-app onboarding checklist and empty states
  37. First ten thousand in MRR review
  38. First SOC 2 Type I audit
  39. Moving early customers onto current plans
  40. First enterprise customer go-live
  41. SaaS metrics pack for a funding round
  42. Post-incident review after a major outage
  43. Vertical SaaS for a traditional industry
  44. Solo technical founder running a micro SaaS
  45. SaaS for small businesses with high churn
  46. Moving from consulting work to a SaaS product
  47. Selling SaaS to customers in several countries
  48. Usage-based or hybrid billing infrastructure
  49. Seat and plan expansion inside existing accounts
  50. Customer success function at a hundred accounts

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Buyer, admin and end-user map for the product

In business software the person who signs, the person who configures and the people who use it every day are often three different people with three different reasons to care. Mapping those roles for your product tells you who the onboarding, the admin screens, the invoices and the renewal email are each written for.

First tasks

  • List who signed, who set up and who uses the product at your five biggest accounts
  • Write one sentence on what each role is measured on at work
  • Mark the screen or document where each role first meets the product
  • Share the map and ask the team which role they design for most

Workspace, seat and account data model

Retrofitting organisations into a product built around single users is one of the most expensive rewrites a SaaS team can face. Deciding early how companies, workspaces, users, roles and seats relate, and what happens when someone leaves a company or belongs to two, saves months of migration later.

First tasks

  • Draw the current relationship between users, accounts and data
  • Write the rule for what happens when an admin leaves a customer company
  • Audit every table for a missing account identifier
  • Add an automated test that tries to read another tenant's records

Subscription billing set-up with a billing provider

Founders who invoice the first customers by hand often find, a year in, that nobody can say which plan each account is on or when it renews. Putting every paying account into a subscription billing tool with plans, billing intervals, tax settings and invoice emails makes revenue countable and collections automatic.

First tasks

  • Export a list of every paying customer with plan, price and renewal date
  • Create each live plan and interval in the billing provider
  • Ask your accountant which tax settings apply to your sales
  • Run an upgrade, downgrade and cancel in test mode and check the invoices

Make it yours.

Install B2B SaaS Startup Building, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.