When to Use

When working with prospects or customers to design how your platform fits into their technical environment — pre-sales, implementation planning, or technical advisory.

Core Jobs

1. Discovery Call Architecture Intake

Questions to ask before designing anything:

Current stack (languages, cloud, databases, auth systems)
Scale requirements (current and projected users/transactions)
Data sensitivity (PII? PHI? compliance requirements?)
Integration requirements (what systems must connect?)
Team capability (who will implement and maintain?)
Timeline and phasing

2. Design the Architecture

Produce a reference architecture diagram:

Data flow (where does data come from, go to, get processed?)
Integration points (APIs, webhooks, SDKs, ETL)
Security boundary (what's in their infra vs yours)

When to Use

When working with prospects or customers to design how your platform fits into their technical environment — pre-sales, implementation planning, or technical advisory.

Core Jobs

1. Discovery Call Architecture Intake

Questions to ask before designing anything:

Current stack (languages, cloud, databases, auth systems)
Scale requirements (current and projected users/transactions)
Data sensitivity (PII? PHI? compliance requirements?)
Integration requirements (what systems must connect?)
Team capability (who will implement and maintain?)
Timeline and phasing

2. Design the Architecture

Produce a reference architecture diagram:

Data flow (where does data come from, go to, get processed?)
Integration points (APIs, webhooks, SDKs, ETL)
Security boundary (what's in their infra vs yours)

Solutions Architecture

When to Use

Core Jobs

1. Discovery Call Architecture Intake

2. Design the Architecture

Solutions Architecture

When to Use

Core Jobs

1. Discovery Call Architecture Intake

2. Design the Architecture

3. Technical Proposal

4. Handle Objections

Key Outputs

Anti-Patterns

Taskflow Inbox Triage

Accessibility

Open a Pull Request

Investor Materials

Continuous Agent Loop

Configure Ecc