Problem
Founders often start with broad ideas but no repeatable way to turn an industry choice into a realistic plan, staffing model, income assumptions, or startup sequence.
R&D case study
Planning system that turns broad startup ideas into structured, traceable business planning steps.
At a glance
Delivery stage
R&D
Current state
Prototype
My role
Sole architect and full-stack engineer
Founders often start with broad ideas but no repeatable way to turn an industry choice into a realistic plan, staffing model, income assumptions, or startup sequence.
Built as an offline-first planning engine backed by the full NAICS hierarchy. The system combines rules-based role generation, income modeling, dependency-ordered startup procedures, and explainability views so users can inspect why each recommendation was produced.
Working planning engine with rules-based role generation, income modeling, and explainability views across NAICS hierarchy
This section shows the operational logic behind the build, not just the user-facing surface.
Core constraint
Explainability: every generated recommendation must trace back to a rule, data source, or constraint, not a black-box model
The planning engine is supported by a documented rules architecture and outputs that show the provenance of each recommendation.
More work at a similar delivery stage.

Lead automation platform designed to handle calls, qualification, and CRM handoff without manual follow-up bottlenecks.
My Role
Sole architect and full-stack engineer
Outcome
Architecture validated with working voice gateway, queue orchestration, and CRM integration layer; advancing toward pilot deployment
Legal intake workflow that screens urgency, gathers structured information, and routes cases without inconsistent or unsafe responses.
My Role
Sole architect and backend engineer
Outcome
Working prototype with policy-gated intake flow, jurisdiction detection, and conflict-check pipeline