Founding Partner Early Access
THE BUSINESS OPERATING SYSTEM FOR TRADES
ATLASS OS
Your business, running on an operating system.
One ledger. One timeline. One API. Every call, text, receipt, photo, hour and dollar lands in the same memory — and every screen has a door your AI can walk through.
Built in Alberta by a roofer; the first customer is his own company.
- One ledger
- One timeline
- One API
Request Founding Partner Access
Current through release 28ec · 14 October 2026
Not four apps that don't talk. An operating system.
QuickBooks for the books, a job app for the jobs, a CRM for the leads and your phone for everything in between — every seam is a leak, and every automation only sees its own app. ATLASS OS runs the whole business on one database: no glue between your own apps, nothing to sync between your CRM, your books and your field crew.
It bends around how your crew already works, and keeps what would otherwise fall through the cracks: an event with nobody to attach to yet is kept, not lost, and adopted the moment its owner is known.
One write path from estimate to job to invoice to payment removes the retyping where errors happen. ScanSnap learns a vendor's receipt layout after three AI-read scans and then reads it without the model; every FieldOps check-in teaches the auto-detector; a crew pick-up the phone cannot prove stays a blank for a person to fill — never silently invented.
One operating system, four parts
Each part is live on production; open any of them for the proof and the release behind it.
The operating system
ATLASS
The operating system your business runs on: one ledger, one timeline, one API.
Real double-entry books and payroll under the CRM, a door for your AI on every screen, and a receipt for every release.
How ATLASS works
How it works
What it streamlines: One write path carries an estimate to the job, the invoice and the payment, so nobody retypes a number into a second app — the retyping is where the errors were.
What runs by itself
- An estimate accepted online books its deposit as a customer deposit (28bn)
- A payment started from an invoice arrives pre-filled and lands applied to it; a bounced cheque reverses everything it touched (PL-1085 · 28dy)
- No estimate, change order or progress bill can bill the same work twice (28cl · 28cn)
- Every door that posts GST refuses a period you have already filed (PL-1072 · 28dy)
What it replaces
- a separate bookkeeping app and the sync that copies invoices into it
- a payroll app fed by retyped timesheets
Runs on: Stripe · Resend · Cloudflare R2
Floors it keeps
- Walled off per business (28aj · tenancy scanner)
- An audit log nobody can rewrite (28l)
- Agent deletes are soft, restorable from trash (28ag)
- Books certified before every release (money-invariants gate · 28dp–28ds)
Status: Live (28dz)
The proof
- Real double-entry books under the CRM, certified by arithmetic that cannot call the code it audits — debits equal credits and the subledgers tie to the ledger before every release. Payroll calculates and records T4s, T4As, ROEs and WCB returns; you file with CRA. (money-invariants gate · 28dp–28ds)
- Every screen has a door: 241 MCP tools serve production (counted October 20, 2026); every work item must answer GUI · MCP parity; a write tool whose endpoint lacks a permission check fails the build. (tool inventory · parity rule · permission gate)
- Every release has a receipt: a 23-item checklist with the exit code of every gate written in the notes, a red recorded on purpose when it is reasoned; an audit log the database itself will not let anyone rewrite. (28dz · 28l)
Disclosed limits: SOC 2-sensitive controls, machine-enforced, not yet audited. The money defect disclosed here, un-applying a discounted credit leaving receivables off the ledger by the discount, is closed (PL-1104, 28ea).
All-Channel Activity Timeline
ACAT
Every call, text, email, receipt, photo and hour, on one append-only timeline and one map — nothing falls through the cracks.
Tagged to the right customer in milliseconds, read and understood in a second pass, never overwritten — on the desktop and on the foreman's phone.
How ACAT works
How it works
What it streamlines: Nobody copies a call, a text or an email into the customer's file: it lands on that customer's timeline by itself, tagged before anyone looks at it.
What runs by itself
- Callers and senders named and tagged by rules in milliseconds, before any model is asked (migration 128)
- Recordings split into speaker turns, then read for intent and sentiment (PL-1091 · 28dy)
- An event with nobody to attach to yet is kept, then adopted the moment its owner is known (PL-684 · migration 195)
- Each location's pipeline drawn on the map, day by day (PL-812 · 28do)
What it replaces
- a separate call-tracking app
- the connector copying call and email logs into the CRM
- notes typed up after every call
Runs on: Twilio · Gmail (Google Workspace) · Google Maps Platform · Cloudflare R2 · OpenAI
Floors it keeps
- Walled off per business (28aj · tenancy scanner)
- Never overwritten: the second pass appends (migration 128)
Status: Live (28dy)
The proof
- Two passes over one append-only table: the first names the caller and tags the record deterministically in milliseconds, before any model is asked; the second reads it, infers intent and sentiment, and appends — never overwrites. (migration 128 · ACAT tagging engine)
- Recordings become speaker turns become tags; the same customer timeline is on the foreman's phone; the map shows each location's pipeline day by day, with sentiment and intent heat. (PL-1091 · 28dy · PL-908 · 28di · PL-812 · 28do)
- Orphan-first: an event with nobody to attach to yet — a canvassed house, an unknown caller — is kept and adopted later, not lost. (PL-684 · migration 195)
Disclosed limits: The inferring layer was dark on production from 22 Sep to 13 Oct; our own refuter found it and the fix shipped in a day (28dx). On the roadmap, not built: a 3D map with a temporal playhead, and ACAT projected onto drone footage.
Business phone, wired into ACAT
S.I.M.P.L.E. PHONE SYSTEM
Your business line, answered, routed, recorded with consent, transcribed — and remembered.
Callers named before it rings, robots stopped at the door, recordings in your own storage, and every call, voicemail and text on the customer's timeline.
The phone system carries the I, M and E of S.I.M.P.L.E.: S — Spatial Intelligence · I — Integrated Marketing · M — Management & Production · P — Production Logistics · L — Ledger & Financials · E — Ecosystem
How the phone system works
How it works
What it streamlines: Nobody writes down who called or what was said: every call, voicemail and text is named and filed on the customer's timeline, and a recorded call is transcribed there.
What runs by itself
- Every call named before it rings; sales robots stopped before any forward, alert or text-back (PL-574 · PL-565 · migration 98)
- Every forwarded call reports what happened on the phone leg (28bc)
- Recordings and voicemail land in your own storage and are transcribed onto the timeline (PL-571 · 28au)
- Staff call and text out through the company number, and the history files itself (PL-575 · 28aw)
What it replaces
- a separate call-tracking or answering app
- voicemail that lives behind a vendor's link
- the connector copying the call log into the CRM
Runs on: Twilio · Cloudflare R2 · OpenAI
Floors it keeps
- Walled off per business (28aj · tenancy scanner)
- Recording disclosed when ATLASS answers (PL-565 · 28aw)
Status: Live (28cp)
The proof
- Inbound routing, forwarding with screen and whisper, an escalation ladder, surge mode, and an operator line so staff call and text out through the company number — the history lands in ACAT. (PL-575 · 28aw)
- Every call named before it rings — carrier name, your own records, a number lookup, a spam directory; sales robots blocked before any forward, alert, text-back or record; the greeting says "recorded" only when the call is. (PL-574 · PL-565 · migration 98)
- Recordings and voicemail kept in your own storage, not a vendor link, and transcribed onto the timeline; the crew texts customers from FieldOps on the business line. (PL-571 · 28au · PL-907 · 28cp)
Disclosed limits: Per-employee customer-facing numbers wait on carrier registration. Photos texted to the main line are an open defect (PL-1111).
The apps around the OS
THE ECOSYSTEM
Atlass FieldOps, ProjectCam, ScanSnap, CanvassCam and Overhead: one API, no back ends of their own, every byte lands in your OS.
Native field apps on the crew's phones and a measurement app at the desk, all writing straight into ATLASS.
How the ecosystem works
How it works
What it streamlines: The crew's hours, receipts and job photos reach the books and the job file without anyone typing them in — and what the phone cannot prove stays a blank for a person to fill, never a guess.
What runs by itself
- Leaving home, crew pick-ups and site arrivals recorded as time events; a presumed break is confirmed with one tap (28bp–28bs)
- A photographed receipt becomes a reviewed bill on the right project (28bs · 28ca)
- Job photos filed to the project with where, when and which way the camera faced (28bz)
- A canvassed street becomes one located house per photo and a mailing with a QR code per house (28cv · 28cw)
What it replaces
- a separate time-clock app and its timesheet export
- a receipt-scanning app and its sync into the books
- a photo app whose pictures never reach the job file
Runs on: Google Maps Platform · AWS Textract · Cloudflare R2 · Twilio
Floors it keeps
- Walled off per business (28aj · tenancy scanner)
- No coordinates on the event record (28bq)
- A field login cannot open the office app (PL-943 · satellite-only gate)
Status: Live (28cv)
The proof
- Atlass FieldOps: your day becomes time events without typing — auto clock-in on leaving home, crew pick-ups, site arrivals, presumed breaks you confirm with one tap, departures confirmed by two precise fixes. Coordinates never sit on the event record. (PL-766 · PL-767 · PL-769 · PL-788 · 28bp–28bs)
- ScanSnap turns a photographed receipt into a reviewed bill on the right project — needs review, never a guess. ProjectCam stamps every job photo with heading and lens. CanvassCam snaps a street, each house a located record before any lead exists. (28bs · 28ca · migration 175 · PL-684 · PL-685)
- Atlass Overhead: drone and phone photos become roof-and-wall measurements and Xactimate-ready quote, report and takeoff PDFs, filed on the project. A field-only login cannot open the office app, by structure. (PL-942 · 28ci · PL-943 · satellite-only gate)
Disclosed limits: Installed on the founder's own phone today; no app-store listing. Overhead's measurement-accuracy study is still ahead — today it files the documents. The full crew-day timesheet and dispatch from the map on the phone are next.
What glued apps structurally cannot do
A receipt becomes a bill
ScanSnap · 28bs · 28ca
Photographed on the phone, read on owned hardware, geocoded, confirmed by a person, and posted as an AP entry in the right project's books.
A call becomes memory
The S.I.M.P.L.E. Phone System · 28aw · 28di
Named before it rings, recorded with consent into your own storage, transcribed, tagged onto the customer's timeline — the same timeline the foreman sees on the roof.
A day becomes a paycheque
Atlass FieldOps · 28bq · 28cf
Leaving home, picking up the crew, arriving on site, lunch, leaving — recorded as time events without typing, and paid by the payroll module in the same database.
ATLASS Satellite Apps
Five apps around one database. Native field apps on the crew's phones and a measurement app at the desk — none of them has a server or database of its own; every byte lands in ATLASS through the same audited doors the desktop uses.
Atlass FieldOps
Field operations
Crew time that tracks itself, check-ins, the crew plan, customer texts from the business line, and each customer's whole history on the phone.
Live · Android
ScanSnap
Receipts into the books
Photograph a receipt; it is read, you confirm what the machine read, and it posts as the right vendor bill — never a guess.
Live · Android · inside FieldOps
ProjectCam
Job-site photos
Full-quality photos filed to the right project with where and when they were taken and which way the camera faced.
Live · Android · inside FieldOps
CanvassCam
Door-to-door
Walk a street and snap each house: every house becomes a location in ATLASS and every street a mailing with a QR code per house. Estimates from the street are coming soon.
Live · Android
Atlass Overhead
Roof & drone measurement
Drone and phone photos become roof-and-wall measurements and Xactimate-ready quote, report and takeoff PDFs, filed on the project in ATLASS with their photos and video.
Live — files into ATLASS · Separate app
Integrations
Built on services you already trust, wired in once, for every business — no glue between your own apps.
Your own AI agent (MCP)
Live
A native MCP server: connect the assistant you already pay for with scoped tokens you mint, revoke and audit. Free on every plan.
Twilio
Live
Your business phone numbers: calls named before they ring, recordings, voicemail and texting from FieldOps.
Stripe
Live
Subscriptions charged by Stripe price ID, read from the same catalog the pricing page shows.
Resend
Live
Estimates, invoices and notifications emailed from your business's own verified address.
Cloudflare R2
Live
Your document and photo archive, in a private bucket a release gate keeps private.
Google Maps Platform
Live
Every location geocoded; roof outlines and street views for measuring and canvassing.
AWS Textract
Live
Receipt reading on the cloud when the owned GPU reader is busy.
Gmail (Google Workspace)
On request
Connect your mailbox the normal way; automatic import is switched on per business while Google's review completes.
OpenAI
Live
Transcription and speaker turns for recorded calls and voicemail.
And also: campaign audiences built from the same memory — sentiment, stage, tags and radius — consent-filtered, with retargeting tiers linked to Google Analytics 4. Nothing is sent to an ad platform yet.
Every release has a receipt
Built with refuters: every change gets an adversarial review, and a release cannot reach production while a gate is red or could not check.
An audit log nobody can rewrite
Database triggers and revoked delete rights, measured before and after on production.
The books certify themselves
Debits equal credits and the subledgers tie to the ledger, checked from raw tables before every release.
Backups that restore
A drill on 4 October 2026 restored 351 of 351 tables and re-certified the books on the copy.
Your business, walled off
Every query is scoped to your business; a scanner fails the build otherwise, and Postgres row-level security backs it up.
- SOC 2-sensitive controls, machine-enforced, not yet audited. No certificates — pursuing them.
- ACAT's inferring layer was dark on production for three weeks. Our own refuter found it; the fix shipped the next day.
- First customer: my own roofing company. Dogfooded on a real crew, not yet validated by other customers. Pre-revenue.
What ATLASS OS does today
Every line below is live on production, with the release that shipped it.
CRM & ACAT memory
- A customer's whole conversation history — calls, texts, email, forms, notes — on the phone (28di · Oct 9)
- Call and meeting recordings transcribed with speaker turns, intent and sentiment (28dy · Oct 14)
- The ACAT map: each location's pipeline, day by day (28do · Oct 10)
- Boards: a project kanban with stages planned against actual (28dy · Oct 14)
- Customer email sent from your business's own address (28bt · Oct 1)
Documents & money
- Estimates accepted online, with the deposit booked as a customer deposit (28bn · Sep 28)
- Receive Payment: apply, re-apply and split; a bounced cheque reverses everything (28dy · Oct 14)
- No estimate, change order or progress bill can bill the same work twice (28cl · 28cn · Oct 7)
- Receipts scanned on the phone post straight to the books (28bs · Sep 30)
- Every door that posts GST refuses a period you have already filed (28dy · Oct 14)
Payroll & crew time
- Pay cheques issued from the screen by cheque or e-transfer, stub emailed (28cf · Oct 5)
- Timesheets as a pay-period grid; the owner's draw splits itself from the books (28bl · Sep 27)
- FieldOps tracking starts itself; the check-in wizard records the crew's day (28bq · Sep 30)
- The crew schedule set and read from the phone (28bt · Oct 1)
Phone & communications
- Calls named before they ring; recording disclosed when ATLASS answers (28aw · Sep 22)
- Every forwarded call says what happened on the phone leg (28bc · Sep 24)
- Text customers from inside FieldOps on the business's own lines (28cp · Oct 7)
- An operator line that dials any number and takes numbers by voice (28bl · Sep 27)
Website & leads
- A canvassed street becomes printed letters with a QR code per house (28cw · Oct 8)
- The letter feeds retargeting — only people who said yes — and the office sees the funnel (28dh · 28dn · Oct 9)
- The Product & Colour Library for your website, every published image stripped of GPS (28dz · Oct 14)
AI & security
- An AI agent can write draft estimates through the same writer as the screen (28dy · Oct 14)
- The assistant asks before deletes, sends and money, and never exceeds your permissions (28ce · 28bb · Oct 5)
- Backups are a release gate; a restore drill matched 351 of 351 tables (28by · Oct 4)
- An audit log the database itself will not let anyone rewrite (28l · Sep 3)
The Value Comparison
Enterprise CRM
per-seat pricing, sold separately from your books
- CRM
- No accounting
- No jobs or scheduling
- Priced per user, in USD
Field-Service Suites
US-priced, per-technician
- Service-trade specific
- No double-entry accounting
- Your books live somewhere else
The "Stack"
(accounting + PM + field-service apps, glued together)
$370–430/month CAD
typical 4-person crew, as compared July 2026
- Disconnected data silos
- Multiple logins, multiple bills
- Integration costs on top
Founding Partners
ATLASS OS
$49/month CAD, flat
Full Pro — locked forever while your subscription stays active.
- CRM with every call, text and email on one timeline
- Estimates, invoices & online acceptance
- Full Double-Entry Books
- Canadian payroll — pay cheques from the screen
- Jobs, Boards kanban & purchase orders
- Business phone: calls named, recorded & transcribed (per-number add-on)
- FieldOps, ScanSnap, ProjectCam & CanvassCam apps
- Website product & colour catalog
- Connect the AI agent you already use
Reserve your spot at /founding — it is secured by your first successful payment when billing opens
Coming soon
Not in the product yet — this is what is being built next, in the open.
A C-suite that is always in the room.
A team meeting whenever you want one. No scheduling conflicts. Each C-suite position is an agent — CEO, CFO, COO, CMO — and each employee has an agent carrying months of operational context on compliance and performance, ready to bring to the board room at the drop of a hat.
Coming soon.
Coming soon
Ava, the executive assistant
Drafts replies to your texts and email for you to approve, honours STOP, and never sends on its own.
Coming soon
Voice captions
Talk while you shoot: ProjectCam and drone-video narration transcribed onto the job as estimating notes.
Coming soon
The full crew-day timesheet
Every crew member's day on one screen, with overrides, built from the events FieldOps already records.
Coming soon
The ACAT map on the phone
Browse, navigate and dispatch from the map in FieldOps.
Coming soon
CanvassCam estimates
Measure the roof from the street and hand the homeowner an estimate on the spot.
Coming soon
Materials library page
Your product and colour catalog published as a page on your own website.
Gmail integration: exactly what ATLASS OS does with your mail
A business can connect its own Gmail mailbox to ATLASS OS. Only the business's owner or an administrator can do it, only by choosing Connect Gmail and approving Google's own consent screen, and it can be undone at any time. Here is the whole of what the connection does and does not do.
What it reads
Incoming mail, so each message appears in your inbox and on the matching customer's timeline. Once automatic import is enabled for your business (today, on request), new mail is imported about every two minutes from the moment it is switched on. You can also run a history import over a date range you choose, or with no dates at all to work through the whole mailbox. The automatic import skips Spam, Trash, Promotions and Social mail and follows the allow and deny rules you set by sender or domain. A history import applies no sender rules and does not skip Promotions or Social mail; Gmail itself leaves Spam and Trash out of the list.
What it changes in your mailbox
It creates two labels and tags each message it imports with one of them, so you can see in Gmail what the CRM has taken in. It moves a message from Spam to your Inbox only when you press Recover. It never deletes mail.
What it sends
Where your business has switched on sending through Gmail (today, on request), every email ATLASS OS sends on your behalf goes out from your Gmail address: invoices, estimates and other documents, payment reminders, marketing and follow-up campaigns and outreach, team invitations, notifications to you (new leads, text-message attachments, call summaries and voicemails), bank-reconciliation reports, and the verification and notice emails sent to people you share documents with. That includes emails sent on a schedule your business configured, such as follow-up sequences and reminders. With sending switched off, none of it uses your mailbox.
What it stores
The automatic import stores, for each message, the sender, the subject, the date, Google's identifiers and a short excerpt (up to the first 1,000 characters of the plain text). A history import stores more: the sender and recipients, the subject, the date, the full text and HTML of the message, and the names of any attachments. Attachments themselves are not downloaded. All of it sits under your business account only, and the Google sign-in credentials are stored encrypted.
When our AI assistant reads it
Mail brought in from Gmail becomes part of your inbox and customer timeline, so the AI features can read it when someone asks. If a user of your business asks the in-app assistant a question that needs those records, or you connect an AI client to your account and it asks for your inbox, what the records contain, including the excerpt of a Gmail message, is sent to our AI model providers or to the client you chose, only to answer that request. The importers themselves do not send mail to an AI provider. It is never used to train AI models.
What it never does
Your mail is never used for advertising, never sold, never shared with data brokers and never used to train AI models. ATLASS OS staff do not read your messages unless you ask us for help and agree, for a security investigation, or where the law requires it.
You stay in control
You can withdraw access at any time at Google Account permissions, and you can ask us to disconnect the mailbox and delete the copies of your mail we hold. The privacy policy has the details.
ATLASS OS's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Become a Founding Partner
$49/month flat for full Pro — locked forever while your subscription stays active, with a direct line to the founder and weighted feature requests. Reserving costs nothing; your spot is secured by first successful payment when billing opens.