This is the production schedule for the aiConnected business plan. Documents are grouped into seven phases. Each phase must be substantially complete before the next phase begins, because later documents depend on the data and decisions established in earlier ones.
Why Sequence Matters
Some documents are foundational — their outputs define inputs for everything that follows. Writing a financial model before completing market research produces numbers without basis. Writing a go-to-market plan before defining the ICP produces strategy without a target. Writing the business plan before any of these are complete produces prose without substance.
The sequence below is designed so that each document can be written with full information from the documents that preceded it.
Phase Overview
| Phase | Focus | Documents | Dependency |
|---|
| Phase 1 | Founding Voice & Identity | 4 | None — start here |
| Phase 2 | Product Foundation | 8 | Phase 1 |
| Phase 3 | Market Intelligence | 10 | Phases 1–2 |
| Phase 4 | Competitive Intelligence | 7 | Phase 3 |
| Phase 5 | Financial Models | 17 | Phases 2–4 |
| Phase 6 | Operations, Technology & Risk | 13 | Phases 1–5 |
| Phase 7 | Go-to-Market & Investor Materials | 19 | All prior phases |
| Final | The Business Plan | 1 | All 78 supporting documents |
Phase 1 — Founding Voice & Identity
These four documents define the language, philosophy, and strategic framing that will appear throughout every other document. They are written first because every other document borrows from them.
1-A. BP-FOUND-01 — Founder Biography & Background
What it is: A 1–2 page narrative biography of Bob Hunter. Not a resume. A story that explains how a non-technical founder built one of the most architecturally sophisticated AI platform concepts in the current market — and why that background is a strength, not a liability.
What it must cover:
- Professional background and relevant experience
- What led to founding aiConnected (the personal “why”)
- How Bob operates: the documentation-first, AI-assisted development approach
- The role of Claude and AI tools in building a solo-founder company of this scope
- Honest framing of the solo founder risk and how it is being mitigated
Source material: knowledge-base/aiconnected-supporting-docs/aiConnected-project-memory-backup.mdx
1-B. BP-FOUND-02 — Company Origin & Mission Statement
What it is: A formal one-page document establishing when the company was founded, why it exists, and what it is ultimately trying to accomplish. This is the company’s north star — used verbatim or paraphrased across the pitch deck, the executive summary, the website, and investor one-pagers.
What it must cover:
- Founding date and original concept
- The evolution from early product ideas to the current platform architecture
- A finalized, single-sentence mission statement
- A finalized, single-sentence vision statement (the 10-year statement)
- The company’s core values and operating principles
Source material: knowledge-base/aiconnected-supporting-docs/aiConnected-project-memory-backup.mdx, knowledge-base/aiconnected-supporting-docs/aiConnected-fundraising-strategy.mdx
1-C. BP-FOUND-03 — Acquired Intelligence Philosophy Document
What it is: A 3–5 page essay articulating why “Acquired Intelligence” is a more accurate, more useful, and more defensible framing than “Artificial Intelligence” — and how this philosophy directly drives every architectural decision aiConnected has made.
What it must cover:
- The distinction between training-based AI and experience-based AI
- The anchor quote: “Any human can be capable of anything, but no human can be capable of everything. And neither can AI.”
- Why persistence, identity, and accumulated experience are the missing layer
- The book outline as background reference
- How ANI (Acquired Network Intelligence) extends this to cross-instance collective learning
- Why this philosophical position creates a defensible product category
Source material: knowledge-base/neurigraph-memory-architecture/acquired-intelligence-rough-outline.mdx, knowledge-base/neurigraph-memory-architecture/ai-terminology-reframing.mdx, knowledge-base/aiconnected-supporting-docs/aiConnected-project-memory-backup.mdx
1-D. BP-FOUND-04 — Two-Layer Strategy Narrative
What it is: A 2–3 page strategic document that explains the deliberate design of the company: a revenue-generating surface layer that funds and trains the cognitive infrastructure layer underneath. This is the document investors will return to repeatedly during due diligence.
What it must cover:
- The surface layer: agency tools as the commercial vehicle
- The foundation layer: Cognigraph as the long-term asset
- Why this structure is intentional and not a pivot
- The data moat flywheel: agencies → users → Cognigraph → better tools → more agencies
- The 2030 robotics thesis: why the training data becomes the most valuable asset
- The GoHighLevel comparison: same surface model, fundamentally different long-term architecture
Source material: knowledge-base/aiconnected-supporting-docs/aiConnected-fundraising-strategy.mdx (Part 3–5)
Phase 2 — Product Foundation
These documents consolidate and formalize the product story. Most of the raw material already exists in the knowledge base — the work here is synthesis, condensation, and filling the documented gaps.
2-A. BP-PROD-01 — Master Product Architecture Overview
What it is: A single document — with one clear diagram — that shows how all three platform layers (Business Platform, aiConnectedOS, Neurigraph) relate to each other, how they share data and infrastructure, and how the developer ecosystem extends all three. This becomes the reference diagram used throughout the business plan.
Source material: knowledge-base/aiconnected-business-platform/aiconnected-platform-overview.mdx, knowledge-base/aiconnected-os/quick-system-overview.mdx, knowledge-base/aiconnected-supporting-docs/aiConnected-fundraising-strategy.mdx (Architecture diagram in Part 3)
What it is: A 2-page condensed overview of the Business Platform — written for a non-technical investor audience. Distilled from the MVP specification and platform overview documents.
Source material: knowledge-base/aiconnected-business-platform/aiconnected-platform-overview-non-technical.mdx, knowledge-base/aiconnected-business-platform/aiconnected-platform-mvp-specification.mdx
2-C. BP-PROD-03 — aiConnectedOS Executive Summary
What it is: A 2-page condensed overview of aiConnectedOS — written for a non-technical investor audience. Distilled from the OS PRD and quick system overview.
Source material: knowledge-base/aiconnected-os/quick-system-overview.mdx, knowledge-base/aiconnected-os/system-standards-and-philosophy.mdx
2-D. BP-PROD-04 — Consolidated 18-Month Product Roadmap
What it is: A single integrated roadmap across all three platform layers — with milestones, dependencies, resource requirements, and the 4-product launch sequence (Knowledge → Chat → Voice → Brain). The 18-week OS build plan and 6-week Voice deadline are reconciled and integrated.
Note: The Voice PRD must be completed before this roadmap is finalized.
Source material: knowledge-base/aiconnected-business-platform/aiconnected-platform-v2-build-plan.mdx, knowledge-base/aiconnected-os/aiconnected-os-prd.mdx (Phase 6 build plan section)
2-E. BP-PROD-05 — Neurigraph Technical Summary (Non-Technical Version)
What it is: A 2–3 page explanation of the Neurigraph memory architecture written specifically for non-technical investors. No code, no database schemas. Uses plain-language analogies throughout.
Source material: knowledge-base/neurigraph-memory-architecture/neurigraph-licensing.mdx, knowledge-base/neurigraph-memory-architecture/object-deconstruction-graph-overview.mdx, knowledge-base/neurigraph-memory-architecture/amygdala-dynamic-heat-threshold-control.mdx
2-F. BP-PROD-06 — Product Status Matrix
What it is: A single reference table covering every product, module, and feature: current build stage, estimated completion date, revenue readiness date, development resource required, and dependencies. Investors use this to pressure-test the roadmap.
Source material: knowledge-base/aiconnected-supporting-docs/aiConnected-fundraising-strategy.mdx (Part 5), knowledge-base/aiconnected-business-platform/production-readiness-checklist.mdx
2-G. BP-PROD-07 — Engine Module Revenue Analysis
What it is: A structured analysis of the 30+ engine modules: which are Tier 1 (launch priority), which are Tier 2 (post-launch expansion), pricing, estimated adoption rates, and projected revenue contribution by year.
Source material: knowledge-base/aiconnected-apps-and-modules/original-aiConnected-engines.mdx
What it is: A comprehensive glossary of all platform-specific terminology — Cipher, Neurigraph, Instance, Persona, Skill Slot, Apprenticeship, Mod, CogniGraph, ODG, ANI, and every other term a reader will encounter in the business plan. Included as Appendix I.
Source material: knowledge-base/aiconnected-os/quick-system-overview.mdx (Glossary section), multiple documents across knowledge base
Phase 3 — Market Intelligence
External data gathering. Some of this requires commissioned research or purchased reports. Items marked with (external) require data from outside the knowledge base.
3-A. BP-MARKET-01 — AI SaaS Market Sizing Report
What it covers: Total market size for AI-powered SaaS tools, growth rate, projected 5-year trajectory. Establishes the macro market context. (External research required — Gartner, Grand View Research, MarketsandMarkets, or similar.)
What it covers: Number of US agencies, current software spend, GoHighLevel’s market share, and the gap in the AI-focused agency platform market. (Partially external — GoHighLevel’s public metrics provide a strong anchor.)
3-C. BP-MARKET-03 — TAM Analysis
What it covers: Total Addressable Market calculation across all three revenue streams: agency platform, aiConnectedOS subscriptions, and Neurigraph licensing. Must show methodology, not just a number.
3-D. BP-MARKET-04 — SAM Calculation
What it covers: Serviceable Addressable Market — the portion of the TAM that aiConnected can realistically serve given its current product scope, geographic focus, and target customer profile.
3-E. BP-MARKET-05 — SOM Projection (Years 1–3)
What it covers: Serviceable Obtainable Market — the portion of the SAM that is realistically reachable in the first three years given team size, capital, and go-to-market approach. Must align with the financial model.
3-F. BP-MARKET-06 — AI Memory Architecture Market Sizing
What it covers: Emerging market for persistent AI memory systems. Mem0’s $24M raise, comparable funding rounds, and analyst projections for the memory infrastructure market. (Partially external.)
3-G. BP-MARKET-07 — Robotics Cognitive Infrastructure Market Research
What it covers: 10-year TAM for the intelligence/cognitive layer of the robotics market. Humanoid robot adoption projections, industrial robotics AI layer spending, and the gap in universal cognitive standards. (External research required — Interact Analysis, IDTechEx, or equivalent.)
3-H. BP-MARKET-08 — Voice AI Market Research
What it covers: Market size and growth rate for AI-powered voice in business contexts — customer service, sales, and receptionist replacement. Validates the Voice AI Hub positioning.
3-I. BP-MKTRES-05 — Agency Customer Discovery Report
What it covers: Structured summary of customer discovery conversations with 10–20 agency owners. Validates the core problem, tests the value proposition, and captures verbatim quotes for the business plan. (Primary research required — Bob must conduct these conversations.)
3-J. BP-MKTRES-06 — Business Client Pain Point Survey & ICP Profiles
What it covers: Survey findings from SMB owners on their current AI tool frustrations. Combined with the Agency ICP and Business Client ICP profiles.
Phase 4 — Competitive Intelligence
All competitive documents are internally written but require current data on competitor pricing, features, and funding. These should be written after Phase 3 market research establishes the market framing.
4-A. BP-COMP-01 — GoHighLevel Deep Dive
Pricing, feature set, agency count, revenue, known weaknesses, developer ecosystem limitations, and why aiConnected is not competing on their turf.
4-B. BP-COMP-02 — ChatGPT Enterprise Competitive Profile
Why persistent, modular, persona-based architecture is categorically different from session-based enterprise AI. Feature-for-feature comparison with emphasis on memory, persona governance, and workflow integration.
4-C. BP-COMP-03 — Mem0 & OpenMemory Competitive Analysis
Mem0: $24M raised, AWS integration, developer-focused positioning. OpenMemory: Apache 2.0, open architecture. How Neurigraph differs from and supersedes both. Why “fork-and-differentiate” is still relevant context.
4-D. BP-COMP-04 — Vapi / Retell / LiveKit Competitive Profile
Voice infrastructure landscape. Why aiConnected is building its own Layer 1 voice infrastructure and what that enables that Vapi/Retell cannot.
How persona-based architecture differs from general agentic task execution. Why “personalities, not agents” is a category distinction, not a feature description.
4-F. BP-COMP-06 — Robotics AI Competitive Landscape
Who is currently attempting to build universal cognitive standards for robotics? Boston Dynamics AI Institute, Physical Intelligence (Pi), 1X Technologies. What each is doing and why aiConnected’s approach is differentiated.
4-G. BP-COMP-07 — Full Competitive Matrix
Single-page visual matrix comparing aiConnected across 12–15 capability dimensions against GoHighLevel, Mem0, ChatGPT Enterprise, Vapi, Manus, and HubSpot. Serves as Appendix D.
Phase 5 — Financial Models
All financial documents require Phases 1–4 to be complete. Revenue models require market size data (Phase 3). Pricing requires competitive context (Phase 4). Unit economics require ICP definitions (Phase 3).
5-A. BP-FIN-09 — Pricing Architecture Document
Written first in this phase because all revenue models derive from pricing. Documents every price point across the entire ecosystem: module floor prices, agency markup guidelines, OS tier pricing, CS package pricing, Neurigraph licensing tiers, and the developer marketplace revenue share.
Six separate revenue model documents, each building on the pricing architecture. Each includes assumptions, variables, monthly projections for Year 1, and annual projections for Years 2–5.
BP-FIN-01 — Business Platform | BP-FIN-02 — aiConnectedOS | BP-FIN-03 — Neurigraph Licensing | BP-FIN-04 — API Resale | BP-FIN-05 — Customer Success | BP-FIN-06 — Developer Ecosystem
5-G. BP-FIN-07 — Use of Funds Breakdown
Line-item budget for the 2.5–3.5M seed round. Maps every dollar to a specific hire, infrastructure investment, or operational need. Must align with the team hiring plan from Phase 6.
5-H. BP-FIN-08 — Neurigraph Licensing Revenue Model
Separate from the general Neurigraph revenue model — this document specifically models the partner licensing business: deal structure, projected partner count by sector, and revenue contribution timeline.
5-I. BP-FIN-10 — Consolidated 5-Year Revenue Projections
Integrates all six revenue models into a single consolidated view. The authoritative revenue number referenced in the business plan.
5-J. BP-FIN-11 — Unit Economics Model
Agency customer: CAC, LTV, LTV:CAC ratio, payback period, expansion revenue assumption. OS user: same metrics for the consumer/prosumer tier. The most investor-scrutinized document in the plan.
5-K. BP-FIN-12 — Break-Even Analysis
Confirms the ~100-agency break-even milestone with supporting calculations. Shows the path to strong profitability at 300+ agencies.
5-L through 5-Q. P&L, Cash Flow, Balance Sheet, Operating Costs, Sensitivity
BP-FIN-13 — Consolidated P&L (Years 1–5) | BP-FIN-14 — Monthly Cash Flow (Year 1) | BP-FIN-15 — Pro Forma Balance Sheet | BP-FIN-16 — Operating Cost Model | BP-FIN-17 — Sensitivity & Scenario Analysis
Phase 6 — Operations, Technology & Risk
These documents require the financial model (Phase 5) and product foundation (Phase 2) to be complete. Hiring plans must align with the Use of Funds.
6-A. BP-OPS-01 — Current Organizational State
Documents exactly what the company looks like today: founder, any contractors, their roles and agreements, current tools and infrastructure. The honest starting point.
6-B. BP-OPS-02 — Organizational Chart (Current & 12-Month Projected)
Two org charts in one document: current state and the post-seed-round structure. Every role labeled with hire timing and budget alignment to BP-FIN-07.
6-C. BP-OPS-03 — Priority Job Descriptions (First 5 Hires)
Full JDs for the first five hires: Senior Full-Stack Lead, VP of Sales, Marketing Director, and two additional roles confirmed through the financial model. Includes title, responsibilities, required experience, and compensation range.
6-D. BP-OPS-04 — Compensation Philosophy & Ranges
Salary bands, equity grant sizes by level, commission structure for sales roles, and the principles governing compensation decisions as the team scales.
6-E. BP-OPS-05 — Advisory Board Structure & Recruitment Plan
Current and target advisory board composition. Credentials needed (technical, industry, investor network). Equity and time commitment structure for advisors.
6-F. BP-OPS-06 — Operational Infrastructure Inventory
Every tool and subscription currently in use, with monthly cost and contract status. DigitalOcean, Supabase, LiveKit, OpenRouter, n8n, Stripe, GitHub, and all others.
6-G. BP-OPS-07 — Development Workflow & QA Process
How code is written, reviewed, tested, and deployed. CI/CD setup, staging environment, version control discipline. Investors evaluate this for execution credibility.
6-H. BP-TECH-01 — Technology Stack Overview
The complete technology stack with rationale for each choice. Frontend, backend, database, voice, AI inference, billing, hosting, and automation layers.
6-I. BP-TECH-02 — Infrastructure Architecture Document
How the platform is hosted and scaled. Container orchestration, load balancing, database sharding, failover, and backup strategy. Written for technical due diligence.
6-J. BP-TECH-03 — Security Architecture Document
Tenant data isolation, memory encryption, containerized module security, API gateway authentication, and the audit event stream. Required before any enterprise conversation.
6-K. BP-TECH-04 — Enterprise Readiness Architecture Checklist
What is already enterprise-ready, what will be added in Phase 3–4 of the GTM, and what requires enterprise-specific configuration. Confirms the “enterprise-aware from day one” claim.
6-L. BP-RISK-01 — Risk Register (Full)
Every identified risk: technical, market, competitive, regulatory, financial, and execution. Each with probability rating, impact rating, and mitigation strategy. The most important risk document.
6-M. BP-RISK-02/03/04/05 — Compliance Assessments
GDPR Assessment | CCPA Assessment | AI Regulatory Risk Assessment | Robotics Regulatory Landscape. Four documents, each addressing a specific compliance domain. Written with legal counsel input recommended.
Phase 7 — Go-to-Market & Investor Materials
The final phase of supporting documents before the business plan is written. These require all prior phases to be complete.
7-A. BP-GTM-01 — Launch Strategy Document
The sequenced launch plan: what launches when, in what order, with what resources, and targeting which customer segment first. Anchors all other GTM documents.
7-B. BP-GTM-02 — Agency Acquisition Playbook
The step-by-step process for signing the first 10, then 50, then 100 agencies. Channels, messaging, objection handling, contract process, and closing. The most operationally critical GTM document.
7-C. BP-GTM-03 — Sales Team Structure & Compensation Plan
The 10-person sales team model. Roles, hiring sequence, base/commission splits, quota structure, ramp expectations, and team management approach.
7-D. BP-GTM-04 — Agency Onboarding Flow & Time-to-Value
How an agency goes from sign-up to first business client live on the platform. Target time-to-value and what happens at each stage.
7-E. BP-GTM-05 — Launch Marketing Plan
LinkedIn announcement campaign, PR strategy, content plan for the first 90 days, and the open-source component launch strategy.
7-F. BP-GTM-06 — Content & Thought Leadership Strategy
How the Acquired Intelligence philosophy becomes a sustained content engine. Blog, LinkedIn, podcast, YouTube, and the book as long-horizon brand builder.
How the developer marketplace is seeded, governed, and grown. Trust pipeline, sandbox environment, revenue share, and community engagement approach.
7-H. BP-GTM-08 — Partner Channel & Integration Strategy
Technology partners, integration partners (CRMs, booking platforms, accounting software), and referral incentive programs.
7-I. BP-GTM-09 — First 10 Agency Target List
Named list of specific target agencies for the initial launch. Each entry includes: agency name, contact information, vertical focus, current tool stack, rationale for fit, and outreach approach.
7-J. BP-GTM-10 — Enterprise Readiness & Progression Plan
The four-phase customer journey from power users to enterprise. What changes at each stage, what features are required, and what the enterprise sales motion looks like.
7-K. BP-GTM-11 — Churn Prevention & Customer Success Strategy
Early warning metrics, intervention protocols, and the white-label CS team playbook for preventing agency and business client churn.
7-L. BP-INVEST-01 — Investor Pitch Deck (Surface Version)
The “GoHighLevel for AI” deck. 12–15 slides. Written for investors who understand agency software economics.
7-M. BP-INVEST-02 — Executive Summary (Standalone 2-Page Version)
The two-page standalone summary sent before a full pitch. Covers: problem, solution, market, model, team, traction, and ask.
7-N. BP-INVEST-03 — GoHighLevel Growth Comparison Study
Documents GoHighLevel’s trajectory — bootstrapped 3 years, then 60MSeriesCat82.7M ARR — and maps aiConnected’s plan alongside it. Validates the model’s credibility with a proven comparable.
7-O. BP-INVEST-04 — Seed Round Term Sheet Reference
A reference guide to standard seed round terms so incoming offers can be evaluated quickly and confidently.
7-P. BP-INVEST-05 — Series A Milestone Definition
The specific, measurable milestones that define Series A readiness: MRR target, agency count, retention rate, Neurigraph architecture status, and team composition.
7-Q. BP-INVEST-06 — Investor Pitch Deck (Deep Version)
The cognitive infrastructure + robotics deck. For sophisticated investors who will evaluate the long-term thesis. Requires all prior documents to be complete.
7-R. BP-INVEST-07 — Data Room Index
The organized index of the investor due diligence data room. Every document in the data room named, categorized, and linked. Ensures nothing is missing when a serious investor begins diligence.
7-S. BP-LEGAL-01 — Entity & Corporate Records Summary
A summary document confirming all legal entity details, IP ownership, and corporate structure — formatted for inclusion in the business plan and the data room.
Final — The Business Plan
Once all 78 supporting documents are complete, the business plan is written as a synthesis document. Each section of the plan draws directly from its corresponding supporting documents. The executive summary is written last.
Target length: 40–60 pages
Format: Markdown (.md) per project document conventions
Quick Reference: Document Count by Phase
| Phase | Documents | Focus |
|---|
| Phase 1 | 4 | Founding voice & philosophy |
| Phase 2 | 8 | Product foundation & synthesis |
| Phase 3 | 10 | Market intelligence & customer research |
| Phase 4 | 7 | Competitive intelligence |
| Phase 5 | 17 | Financial models & projections |
| Phase 6 | 13 | Operations, technology & risk |
| Phase 7 | 19 | Go-to-market & investor materials |
| Total | 78 | Supporting documents |
| Final | 1 | The business plan |
Where to begin: Start with BP-FOUND-01 — the Founder Biography. It is the fastest document to write, requires no external research, and immediately establishes the voice and tone that will carry through every document that follows.
