Conduit33 reads any email — headers, body, signature, attachments — and builds a workspace out of it. Tasks, dates, people, files, a board, typed properties. Then every panel, column and word is yours to change.
Why not just an inbox
The ledger
Conduit33 extracts promises in both directions — decided by who sent the message crossed with whether the sentence is a promise or a request. Overdue first. Every row shows the exact sentence it came from, and closing one records who closed it and when.
The digest
Each workspace remembers when you last looked and tells you what moved since — excluding your own edits, because a change feed full of your own typing is noise. A week away stops being archaeology.
The query
due:<next-week · over:500k · tag:bid · overdue. Once extraction has written typed fields, “which bids are due next week” is a query instead of an afternoon.
Not a summary of the email. The working surface the email implied.
The email
Invitation to Bid — Ridgeline MOB
dana@marlingc.example
Bids are due 8/7/2026 at 2:00 PM. RFIs due 7/31/2026. Coverage needed for concrete, structural steel, drywall… The budget is $14.5M.
Tasks
Key dates
People
Trades
Numbers
Files
A bid invitation should not build the same workspace as a job application. Each recipe decides which panels exist and what goes in them — and you can override the guess, or save your own layout as the new default.
Bid invitation
An ITB or plan-room invite: trades, bid date, plans, RFI cutoff.
Quote received
A price came in: what it covers, what it excludes, what it costs.
Question / RFI
Someone needs an answer. Track the question, the owner, the response.
Meeting
Agenda, attendees, the link, and what came out of it.
Issue / ticket
Something is broken. Triage it, reproduce it, close it.
Candidate
A person to evaluate: resume, loop, scorecard, decision.
Invoice / billing
Money owed: amounts, terms, approval, payment.
Contract / agreement
Redlines, obligations, dates that bind, who signs.
Travel
Itinerary, confirmations, and what to pack for.
Project update
Status in, decisions out, risks tracked.
Intro / outreach
A new relationship: who they are, what they want, what next.
Add, rename, resize, reorder or delete any of them. Your own columns in a table, your own lanes on a board, your own typed properties on anything.
It is kept, unchanged.
The original is stored exactly as it arrived and shown in its own panel. Editing a workspace never rewrites it.
Extraction is deterministic.
The same message always builds the same workspace. A model only ever adds to that, and what it adds is labelled as its own.
Tenants are isolated in Postgres.
Every row carries an org id and every query runs under row-level security, so a bug cannot cross an account boundary.