Theiagen × Galang AI updates
Quote stage automation × SOW generation
July 27, 2026 · Monday update
Built & tested end to end
Theiagen
Client Updates
What changed
What's next
What we need
What changed
The quote intake moved onto the contract page.
Before
A separate Google Form.
- Filled in by hand, every time
- A second tool to open
- Answers sat outside the contract record
→
Now
Everything on the Notion contract page.
- Contract ID, client details, and anything else already in Twenty or Notion fills itself in
- The few remaining questions sit on the contract page. No Google Form
- Answer them, click Generate, and the Quote and SOW land in Drive
You fill in just four things:
prepared by · standard sections · describe the work · services
✓Built and tested end to end in the sandbox.
What changed
What's next
What we need
The whole picture
Where today's piece sits in the full flow.
Nine stages from a lead arriving to renewal. The first four run live today. Stages 5 to 8 already have draft code and are in testing.
1Lead intake
Contact, company and lead created in Twenty, mirrored to Notion
Live
2Lead
Partner token set, deal opens
Live
3Discovery
Client account and qualified lead created
Live
We are here
4Quoting
Contract page and questions, then generate the Quote and SOW
Live today
5Procurement
Slack ping for the compliance checklist and action items
Testing
6Signed
Work types and financials created
Testing
7Active
Hours and burn tracked against the contract
Testing
8Renewal
Renewals and amendments
Testing
9AI
AI automations on top of the flow
Planned
Live and running
Today's update
Draft code built, testing, not live yet
Planned, not built
What changed
What's next
What we need
What's missing, and what we'd build next
The file name is the switch.
Today the trail stops when Greg sends the quote. Nothing tells the system the client said yes. The fix reuses something your team already does: renaming a file in the contract's Drive folder.
Rename the file, and the rest happens on its own
| The file name says | What happens on its own |
|---|---|
..._APPROVED |
Quote status set to approved, the date stamped, the deal moves on in Twenty, Slack pings the team, and Procurement starts. Code already drafted |
..._SIGNED |
Contract marked signed, the date stamped, work types and financials created. Also already drafted |
..._v2 ..._v3 |
Treated as a new version. The earlier one is kept, never overwritten |
..._DECLINED |
Quote closed out, deal marked lost, and Slack asks once for the reason |
| nothing renamed | The reminder goes out instead |
Three gaps that go with it
A reminder that makes it happen
When a quote is marked sent, a Notion comment and a Slack message carry the exact file name to copy and paste. Nothing to remember. If nothing is renamed after 5 working days it nudges weekly, three times, then flags Greg once and stops.
A "Mark as sent" link
Right now nothing records the day a quote actually went out, so the 30-day Valid until date passes unnoticed. One click on the contract page, the same trick as Generate, stamps the date and starts the clock.
Someone to chase the quiet ones
Nudges to the deal owner at day 7, day 21, and 3 days before the quote expires. Plus one Notion view of every open quote: who owns it, when it went out, how long it has been waiting.
✓
None of this is a big build. It reuses what is already running: the 15-minute background check, the Slack pings, the per-contract Drive folder, and the status fields on the contract page. The only new idea is treating the file name as the switch.
What changed
What's next
What we need
What we need from you
Five questions for you.
1
Does this match how you actually work?
Now that you've seen the quoting and SOW flow, is anything missing or off?
2
Do you ever sign inside a tool?
DocuSign, Adobe Sign, anything like that. If you do, the signature itself is a cleaner trigger than a file name.
3
How should leads actually arrive?
Has this been finalised? It decides what feeds the top of the pipeline.
We don't want to build the wrong door.
4
Who owns each part, and who needs Twenty?
We have a first guess for all eleven steps. We'll send the table over for you to confirm or correct.
So the automations and permissions match how you really work.
5
Walk us through one real procurement.
Start to finish: what actually happens from "client agrees to the quote" to "signed"?
This is the next thing we build.
01 / 05