I build founder-facing operating systems for early-stage startups.
Currently building Founder OS: practical workflows that help founders turn messy GTM, RevOps, customer, product, hiring, AI workflow, and investor signals into decisions.
Public-safe proof of work showing how I structure messy startup operating problems into lightweight systems, decision artifacts, and founder-ready operating cadences.
At STEMpedia, I built RevOps infrastructure from scratch across CRM architecture, pipeline stages, handoffs, automations, reporting, and CEO visibility. That operating experience is the base layer behind this Founder OS portfolio.
| If you are | Start here | Why | First file to open | CTA |
|---|---|---|---|---|
| Founder with broken CRM or handoffs | revops-infrastructure-playbook | CRM hygiene, pipeline visibility, handoffs, automation logic, and CEO reporting. | templates/crm-hygiene-audit.md | Copy the audit or open templates/weekly-ceo-briefing-note.md. |
| Founder improving D2C revenue | dorje-teas-d2c-revenue-growth-os | Weekly D2C revenue cadence across funnel, product, channel, retention, and margin. | EXECUTIVE_SUMMARY.md | Read EXECUTIVE_SUMMARY.md or 07_founder_review_system/weekly_revenue_review_memo.md. |
| Founder losing sales-call learning | founder-led-sales-call-os | Turns messy call notes into objections, deal risk, rescue actions, and narrative tests. | outputs/weekly_sales_learning_memo.md | Open the weekly sales learning memo. |
| Founder unsure what to automate | founder-ai-workflow-roi-os | Ranks workflows by AI ROI, risk, payback, and hire-vs-automate logic. | outputs/founder_ai_roi_memo.md | Open the founder AI ROI memo. |
| Founder with messy onboarding | founder-customer-onboarding-os | Finds closed-won customers stuck before activation. | outputs/founder_onboarding_memo.md | Open the founder onboarding memo. |
| Founder preparing investor updates | board-pack-investor-update-agent | Turns metrics into board narrative, risks, decisions, and investor update drafts. | docs/demo_output/board_pack.md | Open the demo board pack. |
| Founder trying to turn expertise into business conversations | founder-visibility-os | Turns founder POVs, proof-of-work, and operating lessons into visibility, attribution, and repeatable content cadence. | templates/copy_this_into_sheets.md | Copy one table, fill 10 rows, and run one weekly visibility review. |
| Non-technical operator | founder-os-adoption-kit | No-code templates, prompts, sample inputs, and sample outputs. | START-HERE.md | Start with one kit. |
| Hiring manager | revops-infrastructure-playbook | Closest repo to real operating work. | outcomes/results.md | Review outcomes and architecture. |
| Technical operator | Any executable Founder OS repo | Most executable repos include sample data, config, outputs, tests, and a Makefile. |
Makefile, tests/, and outputs/ in the selected repo |
Run the demo or inspect tests. |
These six are the strongest proof repos. They should be inspected before supporting analytics or market projects.
| Priority | Repo | Why open it |
|---|---|---|
| 1 | revops-infrastructure-playbook | Closest to real operating work and measurable RevOps impact |
| 2 | dorje-teas-d2c-revenue-growth-os | Public-safe D2C revenue-growth system with funnel, lifecycle, pricing, and operating artifacts |
| 3 | founder-led-sales-call-os | Post-call sales intelligence for objections, deal risk, rescue actions, and founder learning |
| 4 | founder-ai-workflow-roi-os | AI workflow ROI and automation readiness before building deeper automation |
| 5 | founder-customer-onboarding-os | Customer onboarding and activation system for founder attention, risk queues, and handoffs |
| 6 | board-pack-investor-update-agent | Founder and investor communication |
| Repo | Use case |
|---|---|
| founder-hiring-talent-pipeline-os | Hiring decisions, scorecards, trial projects, reference checks, and founder hiring memos |
| startup-metrics-playbook | Shared metric definitions for dashboards, board packs, weekly reviews, and RevOps reporting |
- founder-os-adoption-kit: no-code starting point with starter kits, templates, prompts, and sample outputs.
- founder-os: umbrella map for how the modules connect.
Use one kit or one repo first. Do not adopt the full system on day one.
Founder OS helps founders operate better. Founder Visibility OS helps founders explain operating insight to the market.
Use founder-visibility-os when proof-of-work, GTM learnings, RevOps lessons, product signals, hiring lessons, or investor narratives should become founder-facing visibility and business conversations.
This is optional. Do not adopt it before the core operating workflow is useful.
| Visitor | Best next action |
|---|---|
| Founder | Pick one operating problem from the role table, open the matching repo, and read the first founder-facing artifact. |
| Hiring manager | Start with revops-infrastructure-playbook, then inspect one synthetic Founder OS repo that matches the role. |
| Technical operator | Open an executable repo, inspect Makefile, tests/, sample inputs, and committed outputs before running anything. |
| Non-technical operator | Start with founder-os-adoption-kit, copy one template, and use the sample output format before touching code. |
These repos are not meant to show tool usage alone. They are meant to show how I structure ambiguous operating problems into:
- inputs
- scoring logic
- decision artifacts
- owner actions
- weekly cadence
- founder-ready communication
For the full module map, operating lifecycle, and stack combinations, open founder-os.
The profile is the front door. The detailed map lives in founder-os so this page stays easy to scan.
Sample data is synthetic, anonymized, template-only, or based on public sources where documented. Do not put private company, customer, prospect, employee, investor, merchant, borrower, payment, or internal operating data into public forks.
- GitHub: shubham1502-hue
- LinkedIn: Shubham Singh