FOR FOUNDERS

Give the software project a clear foundation before more building begins

Airchor helps founders turn an early idea or existing prototype into structured scope, assumptions, architecture direction, roadmaps, and developer-handoff drafts.

Airchor organises supplied context. It does not currently validate the market, inspect code, verify architecture, or execute implementation.

Founder route: define the project foundation before the next build cycle.
  1. Problem and first user
  2. Scope and exclusions
  3. Project Blueprint
  4. Builder handoff

THE AUDIENCE PROBLEM

Fast building can hide unclear decisions

A prototype can appear quickly while the first user, product boundary, architecture assumptions, risks, and next development step remain undefined. The result is often another sprint or prompt built on uncertain foundations.

LIVE

Create New Project

Use this route when the main task is defining what should be built.

Capture the problem, target users, proposed solution, scope, exclusions, features, architecture assumptions, risks, roadmap, evidence context, assumptions, and missing information.

FOUNDATION → VISION

Founder orchestration motif

  1. Problem
  2. First user
  3. Scope
  4. Blueprint
  5. Approved build direction
A founder’s problem, user, boundary, assumptions, and evidence become a reviewable Blueprint before future governed implementation.
Read visual as text
  1. Problem
  2. First user
  3. Scope
  4. Blueprint
  5. Approved build direction

Define → bound → evidence → handoff

LIVE ROUTE MAPPING

Choose the route that matches the project

Use Create New Project when the software does not yet exist or still needs to be defined. Use Work on Existing Project when an application, prototype, inherited repository, or deployed product already exists and requires structured assessment or continuation planning.

ROUTE 01LIVE

Create New Project

Use it when the software does not yet exist or when the main task is defining what should be built.

Output package

A 14-document Project Blueprint.

Explore Create New Project
ROUTE 02LIVE

Work on Existing Project

Use it when a prototype or application already exists and needs structured assessment, continuation planning, or a repair-versus-rebuild discussion.

Output package

A 10-document Assessment & Recovery Plan.

Current boundary: The assessment is based on supplied and manually reviewed context. Airchor does not currently inspect repository code, reproduce failures, run tests, or verify deployment state.

Explore Work on Existing Project

CURRENT WORKFLOW

How Airchor works today

  1. Provide structured project context.

  2. Separate known information, assumptions, evidence, gaps, and risks.

  3. Apply deterministic rules to readiness, confidence, evidence strength, and next actions.

  4. Create the relevant persistent Markdown document package.

  5. Inspect the documents, limitations, warnings, and staleness.

  6. Download eligible documents for developer, agency, advisor, or coding-tool review.

CURRENT OUTPUTS

What Airchor can help prepare

The Blueprint is generated from user-provided context and deterministic templates. Architecture, pricing, market, testing, and implementation statements remain advisory drafts until reviewed.

  • A clearer problem and first user
  • A defined scope and explicit exclusions
  • Feature priorities and rationale
  • Architecture assumptions and risks
  • A staged roadmap
  • Visible assumptions and missing information
  • A testing and validation direction
  • A builder or developer handoff draft
Create New Project14

Project Blueprint

  • Project Scope and Output Boundary
  • Feature Prioritisation
  • Technical Architecture
  • Sprint 001 Builder Handoff

Reviewable Markdown drafts based on saved inputs and deterministic rules.

SYNTHETIC EXAMPLE

Northstar Volunteer Scheduling

A browser-based scheduling workspace for volunteer coordinators who currently manage availability, shift requests, and confirmations through spreadsheets and email. The first version should support coordinator-managed events, volunteer availability, assignment review, and confirmation. It must not include payroll, public social networking, or complex workforce management.

Target user

  • Volunteer coordinators at small charities and community organisations.

First scope

  • Coordinator sign-in
  • Event creation
  • Volunteer availability
  • Shift assignment
  • Confirmation status
  • Simple dashboard

Explicit exclusions

  • Payroll
  • HR records
  • Public volunteer marketplace
  • Native mobile applications
  • Complex analytics

Synthetic planning scenario. Northstar Volunteer Scheduling is not a customer or testimonial.

CURRENT LIMITATION

Current planning support has clear boundaries

Airchor does not validate product-market fit, architecture feasibility, technical estimates, or implementation automatically.

  • No product-market fit validation
  • No architecture-feasibility verification
  • No technical-estimate verification
  • No implementation execution
PLATFORM VISION

From project foundation to governed implementation

Future Airchor is designed to carry approved scope, evidence, architecture, permissions, and acceptance criteria into controlled agent execution and independent verification.

Governed execution is planned, not current MVP functionality.

MVP v1.0 · LIVE

Airchor helps founders turn an early idea or existing prototype into structured scope, assumptions, architecture direction, roadmaps, and developer-handoff drafts.