How Architect actually works

Five steps from blank workspace to live CRM.

No abstract concepts. This is the literal flow: open, describe, build, refine, ship.

01

Tell Architect what your business does

Open the AI panel and describe your operation in plain English. "I run a solar installer. M1 fires after permits, M2 after install, M3 after PTO. Sales reps own pipeline; install techs see only their assigned jobs."

The AI emits configuration calls — not UI code. Every primitive it generates is a real, native Architect object: features, fields, stages, triggers, permissions.

Architect AIYOU · 2:14 PMI run a solar installer. Build me aCRM with M1/M2/M3 milestone gates.ARCHITECTGot it. Building "Pipeline" with stages:Lead → Site Survey → Contract →M1 → Install → M2 → PTO → M3.Each milestone fires the dealer feeautomatically. Ready to preview →Ask anything about your CRM…PIPELINE · LIVE PREVIEWSTAGE 1LeadSTAGE 2Site SurveySTAGE 3ContractSTAGE 4M1STAGE 5InstallSTAGE 6M2STAGE 7PTOSTAGE 8M33 milestones complete · dealer fees fired automaticallyApply to my workspace
The AI lives inside Architect. It edits your real workspace.
02

See your CRM appear in real time

As the AI emits configuration, your workspace populates. Cards snap into the grid. Tabs slot into the right order. Fields appear with the right types and bindings.

Nothing is rendered by the AI directly. Every screen is Architect rendering its own configuration — which means it can't produce a broken layout, ever.

Workflow Builder+ Add featurePipelineHeader Position 1Feature Type: Menu ViewPre-InstallHeader Position 2Feature Type: Menu ViewInstall DayHeader Position 3Feature Type: Menu ViewPost-InstallHeader Position 4Feature Type: Menu ViewEquipmentHeader Position 5Feature Type: Menu ViewFinanceHeader Position 6Feature Type: Menu View
Workflow builder, generated from a 30-second prompt.
03

Refine in the same view your team will use

Click any field to edit it. Drag any section to reposition it. Add a tab and watch it appear where it'll live. Resize a field from any edge — the grid snaps cleanly, neighbors reflow to the next row automatically.

There is no "switch to preview mode." There is no separate builder window. You are already in the screen your team will use every day. The only difference is the edit affordances are showing.

OverviewDetailsInstall+ FeatureACustomer Name@EmailRegionStageOwnerSystem AddressNotes!Priority
Tab View Builder — drag from any edge, drop into any slot.
04

Wire your data — manual or live

For every field, pick the source. Manual lists you control, live pulls from HubSpot, Stripe, your HR system, your own API. The pattern is the same everywhere because it's the same primitive.

If you're migrating from another CRM, hit Import. OAuth into HubSpot / Salesforce / Pipedrive / etc., confirm the mappings Architect proposes, commit. Schema, data, and workflows arrive together in under an hour.

FIELD SOURCES
Manual list
"Lead, Site Survey, Contract..."
Ready
REST API
GET https://api.yours.com/regions
Ready
OAuth import
Pull from HubSpot every 5 min
Ready
CSV upload
One-shot, 12,400 rows
Ready
Linked record
Pull from Contacts.email
Ready
Five field sources: manual, REST, GraphQL, CSV upload, OAuth import.
05

Ship it to your team

Set permissions: row-level, column-level, view-level. Sales reps edit early-stage deals; ops sees install records but not commissions; install techs see only their jobs.

That's it. Your team opens Architect and uses the exact thing you built. They can run it offline. They can collaborate live. They can chat in the workspace shell. The CRM you configured is the CRM they ship from.

Owner
Everything
1 users
Admin
Everything except commissions
3 users
Sales Rep
Pipeline stage <= Contract
12 users
Install Tech
Assigned jobs only
8 users
Viewer
Read-only · public dashboard
4 users
One product. One mental model. Builder = use.

Try it. From sign-up to your first record, under ten minutes.