Design your Growth OS | FounderGrowthOS

01 · Business

What are we building around?

The commercial reality first. The system should fit your business, not force a template onto it.

Your name *

Work email *

Company *

Your role

Website *

What do you sell, to whom, and at roughly what price? *

02 · Jobs

Which work should the system own?

Choose only what would materially change your week. Amy will challenge the selection if the dependencies are wrong.

Acquisition + CRMFind, qualify, prepare outreach, track conversations and next steps.

Content + distributionPlan, draft, repurpose, schedule and learn from channel performance.

Social engagementFind useful conversations and prepare native replies for approval.

SEOFind demand, build useful pages and learn from search performance.

PR + visibilityTrack podcasts, press, communities and speaking opportunities.

Meta adsPrepare creative, targeting, budgets and controlled launch decisions.

What is painful or repeatedly slipping today? *

03 · Strategy

Give it enough judgment to be useful.

These answers become machine-readable gates, not forgotten kickoff notes.

What measurable change matters in the next 90 days? *

Who is the ideal customer—and who is explicitly not a fit? *

What makes “now” the right time?

Who or what must never be targeted?

What proof can the system use?

04 · Voice + judgment

Show us what “good” actually means.

This is the core calibration layer. Generic tone adjectives are not enough.

Paste 3–5 real examples you would happily send or publish *

What makes copy feel AI-written to you?

Paste one example you rejected and why

How should your voice change by channel?

05 · Systems + boundaries

What should connect—and who decides?

Do not paste passwords, API keys or tokens. Account consent happens later inside the private connector hub.

GoogleGmail, Calendar, Analytics or Search Console.

LinkedInCompany, people, content and permitted publishing.

MetaInstagram, Facebook, WhatsApp or ads.

XContent, signals and engagement.

WorkspaceNotion, Slack or another operating record.

Website + searchCMS, analytics and search performance.

Who approves external actions? *

Preferred approval surface

Sensitive boundaries or permission rules

Safety default: every external send, publish or spend remains approval-only. The installation starts in observation mode and must pass connector, voice and acceptance gates before activation.

06 · Review

Your design brief.

Amy reviews this personally. The next step is a scoped system design—not an automated checkout or a surprise connection flow.

I agree that FounderGrowthOS may use this information to assess and scope the requested installation.

No account credentials are collected here. No engine is activated and no external action is taken from this form.

What are we building around?

Which work should the system own?

Give it enough judgment to be useful.

Show us what “good” actually means.

What should connect—and who decides?

Your design brief.

Design brief received.