Documentation · Architecture

Studio reference

How we think. How it's built.

The principles and structure behind every OpenForm system.

01

Philosophy

Six rules every system follows.

  1. 01

    Rules before models

    Plain rules handle what rules can. AI is added only where it earns its place.

  2. 02

    One record

    Every inquiry, booking and estimate writes to the same customer record.

  3. 03

    People decide money

    Prices, exceptions and complaints always reach a person.

  4. 04

    Everything stops

    Every sequence ends on a reply, a decision or an opt-out.

  5. 05

    You own it

    Accounts, data and credentials live in your name.

  6. 06

    Measured, not assumed

    Each system ships with the numbers that show it works.

02

Architecture

Six layers, from first contact to the report.

  1. L1

    Channels

    Where work arrives

    • Website forms
    • Booking requests
    • Agreed inbound channels
  2. L2

    Record

    One source of truth

    • Customer
    • Inquiry
    • Booking
    • Estimate
  3. L3

    Logic

    Rules that decide

    • Scoring
    • Routing
    • Duplicate checks
    • Stop rules
  4. L4

    Actions

    What the system does

    • Acknowledgments
    • Owner alerts
    • Follow-ups
    • Calendar events
  5. L5

    People

    Where judgment sits

    • Review queue
    • Overrides
    • Pricing
    • Exceptions
  6. L6

    Reporting

    What gets measured

    • Response time
    • Conversion
    • Pipeline value

03

Data flow

How one inquiry moves through the layers.

  1. Step 01

    Capture

    Forms, calls and messages write to one record.

  2. Step 02

    Qualify

    Rules score urgency, value and fit.

  3. Step 03

    Route

    The owner is alerted with the next step.

  4. Step 04

    Follow up

    Timed messages run until a reply, booking or stop.

  5. Step 05

    Report

    Response time, conversion and pipeline value.

04

Control points

Where a person can see and step in.

Triggers
Each automation has one written trigger. Nothing runs without it.
Overrides
A person can pause, edit or stop any step.
Failures
Failed sends are logged and flagged to the owner.
Audit
Changes to a record keep who, what and when.
Consent
Captured with a timestamp on every form.

05

Boundaries

Where it runs and what it will not do.

Runs in
Your accounts: CRM, calendar and email.
Integrations
Official APIs and connectors only. No scraping.
AI
Agreed in writing, labelled to customers, reviewed before it goes live.
Costs
Software, SMS, voice and AI usage billed separately, at cost.
Handover
A written workflow map for every trigger, rule and message.

Map your workflow.

Tell us how work moves today. We'll show where it fits.

Start a project