Dispatch every emergency loss within 15 minutes
Every Emergency-level loss has a crew lead assigned and en route within 15 minutes of the first call.
- Timeframe
- Q1 2027
- Owner
- Alex Smith
Tell Architect how your company operates. It builds your data model, workflows, views, and dashboards — then evolves them as your business changes.
14-day Architect Pro trial · No credit card required · See how it works
Architect starts with how your business actually runs, and builds the structure from there.
Answer a short interview in your own words: what you sell, who you work with, how work moves from the first call to getting paid.
From your answers, Architect proposes the Entries you track, the Flows work moves through and the Properties on each.
Rename, remove or add anything before it exists. Nothing is created until you approve it.
Your team works from views built on that Blueprint — tables, kanban boards, calendars and dashboards.
Later, as the business changes, Architect proposes changes to the same Blueprint. See how changes work
Architect knows your Blueprint — your Entries, Flows, Intents and Playbooks. Ask it a question in plain words, or describe a change, and it answers from your workspace.
Architect chat is included in Pro and in the trial. In the demo workspace, Architect answers from a rule-based engine rather than an AI model.
When the business changes, say so in plain words. Architect drafts the exact changes to your Blueprint and shows them to you before anything happens.
Atlas/An Architect technology
Most CRMs record what already happened. Atlas also holds what your business is aiming for, how your team does the work, and what has to be in place first — connected to the Flows and entries you already use.
Intent
Where are we going?
Write the objective in plain words: what you want to achieve, by when, and who owns it. It becomes the reference point the rest of the work connects to.
Playbook
How do we get there?
A Playbook holds the steps, checklists and judgment calls your team follows. Connect it to the objective it serves and to the Flow where that work moves.
Dependency
What does it depend on?
Most connections only say two things are related. A dependency says one can't start until the other is ready — so you record it only where that's true.
Every Emergency-level loss has a crew lead assigned and en route within 15 minutes of the first call.
Needed before: Dispatch every emergency loss within 15 minutes
Intent
Where are we going?
Write the objective in plain words: what you want to achieve, by when, and who owns it. It becomes the reference point the rest of the work connects to.
Every Emergency-level loss has a crew lead assigned and en route within 15 minutes of the first call.
Playbook
How do we get there?
A Playbook holds the steps, checklists and judgment calls your team follows. Connect it to the objective it serves and to the Flow where that work moves.
Connected to the objective and to its Flow
Dependency
What does it depend on?
Most connections only say two things are related. A dependency says one can't start until the other is ready — so you record it only where that's true.
Needed before: Dispatch every emergency loss within 15 minutes
Hitting 15 minutes depends on dispatchers following the intake steps of the water response.
From the Northstar Restoration Group demo workspace
You don't start from a blank page
Architect's onboarding interview proposes a first objective, a draft Playbook and the prerequisites you confirm.
You review and edit each one. Nothing is created until you approve it.
See your Intents, Flows, Playbooks and Entries in one place, and what depends on what. Open a dependency to read why it exists, and check what a change would touch before you make it.
Entries hold what you track — claims, jobs, clients, invoices. Flows follow work as it moves. Every Entry has its own page with its Properties, tasks, notes and files.
Connect Gmail, Google Calendar and Google Contacts. Calendar and Contacts are read-only. Other connectors aren't available yet.
Threads appear on the Entries they belong to.
Read-only. Your schedule next to the work.
Read-only. Match people you already know to Entries.
Turn any Entry into a report — counts, sums, averages and charts — then arrange reports into dashboards and choose how wide each one is.
Every Blueprint comes from its own interview, so a restoration contractor and a consulting firm end up with different Entries, Properties and Flows.
A complete Architect workspace for a restoration contractor — claims, jobs, estimates, Intents, Playbooks and the Map. No sign-up; everything you change stays in your browser.
Every workspace starts with a 14-day Architect Pro trial. No credit card required.
A traditional CRM gives you a fixed set of objects and asks you to fit your business into them. Architect starts from a conversation about how your company works and builds the Blueprint from that: the Entries you track, the Flows work moves through and the Properties on each. When the business changes, Architect proposes changes to that structure instead of leaving you to rebuild it.
Every new workspace starts on a 14-day Architect Pro trial, with every Pro feature included. No credit card required. When the trial ends, your workspace, Entries and Blueprint stay exactly as they are. Pro features such as Architect chat, Intent, Playbooks, Dependencies and the Architect Map lock until the workspace is on a paid plan.
No. You can sign up with any email address, or continue with Google.
Yes. Export a CSV from your current CRM or spreadsheet and import it into any Entry. You map each column to a Property and review the result before anything is written.
No. Architect proposes changes; it never applies them on its own. Nothing in your workspace changes until you review the proposal and approve it.
Architect shows the exact changes it intends to make — what would be added, renamed or removed. On Pro, you can also see what the change touches: the Flows, Intents and Playbooks connected to it. You approve, edit or discard it.
Yes. Invite teammates from the workspace as Admins, Members or Viewers. Plans are priced per user.
No. Architect works the same way for a team of three or a team of thirty, because the structure comes from how your business operates rather than from its size. Larger teams can work with us on setup and data migration through the Business plan.
Architect drafts changes to your Blueprint; you review and approve each one.
Each workspace's data is separated in the database with row-level security tied to membership.
Google tokens are encrypted on the server, and Calendar and Contacts are read-only.
Read more on our Security page, in the Privacy Policy and the Terms of Service.
Start with a 14-day Architect Pro trial. No credit card required.
Already have an account? Sign in