Month-end close, exceptions, the board pack
The agent pulls the numbers, ties them to the ledger and queues only what doesn't match. Your controller reviews a short list instead of rebuilding the sheet.
NetSuite · QuickBooks · Ramp · Sheets
AI agents for finance, ops and contracts
An agent that runs the department. One engineer, twelve weeks, inside the tools you already pay for.
We sit with the team that owns finance, ops or contracts, cut the work down to what actually has to happen, then ship an agent that runs what's left.
Week 4 is a real exit. If the agent can't clear the threshold on your own past cases, we stop and you keep the map.
The engineer who embeds with you has shipped at
Google
General Motors
BAE Systems
Superhuman
Auction.comOur own contracts desk
Now they take 7 to 15. Our contracts took 30 to 60 days.
Dozens of contracts and change orders a week, with two founders in the middle of all of it — drafting, chasing redlines, pushing signature envelopes. We deleted most of the process, settled on a handful of templates, and built an agent we call Lex. It drafts, redlines what comes back, sends for signature and chases it. It stops and asks a person when it isn't sure. Ops owns it now.
7–15 days
to signature
Down from 30 to 60
Most contracts now close inside two weeks instead of two months.
Under 2 hrs
a week
Down from 10+
Ops owns the queue. Neither founder is in it any more.
Dozens
handled a week
Contracts and change orders
Drafted, redlined, sent and chased without a person starting it.
6–8 months
no counsel
No lawyer in the loop
Lex escalates to a human only when the terms are genuinely new.
This is our own back office, not a client case study. We built Lex for ourselves first, with the same five gates and the same twelve weeks we would run inside your finance or ops team.
About us
We've been building for these teams since 2018. The agent practice is newer. Lex is the first thing it produced.
270 companies. Supervisible, our own product, moved project profitability 40%. We are 50+ people, and for every client one or two directors are in the work rather than on a status call.
DoorDash
Raycast
SamCart
Atoms
Conekta
Bitso
Klar
FortellThey guided us in the right direction, contributed to the source code, wrote articles, and put in place a sustainable content strategy. Alberto and the team were a pleasure to work with.
Pedro Duarte
Hype @ Raycast
What we take on
Start with the department that hurts. One department, one agent, one engineer.
You don't have to pick before the call. The right one is usually the department where the same problem comes up every month and everyone has stopped mentioning it.
Handoffs, the shared inbox, the status chase
The work that sits between two tools until somebody forwards it. The agent moves it, updates the record, and tells a human when it can't.
Gmail · Slack · HubSpot · Notion · Sheets
Draft, redline, send, chase
This is Lex. Templates in, drafts out, redlines handled, signature chased. Escalates when the terms are new.
Drive · DocuSign · your templates
How we work
We don't automate first. Automating a bad process only makes it fast and wrong.
Most of the win is in gates two and three, before a model is involved at all. By the time we automate there is less work left to automate, which is why the agent still works in month nine instead of quietly getting routed around.
01
Question
Why does this step exist? If nobody owns it, it doesn't.
02
Delete
Cut every step that isn't load-bearing. This is where most of the time comes back.
03
Simplify
One path, one owner, no “it depends”.
04
Speed
Write the cycle time down. You can't improve a number nobody keeps.
05
Automate
Last. The agent takes the path that's left and asks a human when it isn't sure.
Week by week
Then it's in production. Not a pilot, not a demo, not a deck.
Tomorrow your engineer is on your channel. Day 10 you have the map. Day 30 you decide whether we keep going.
sit with the operators
The last ten runs
Mostly the ones that went wrong. You get a map of the process and a baseline you didn't have before.
eval before we build
Your own past cases
A threshold agreed in writing. If the agent can't clear it, we stop and you keep the map.
the agent is live
In your accounts
Under your permissions, reviewed with your team every two weeks, handed over as it lands.
Bring one department to a 30-minute call. We'll tell you on that call whether an agent belongs in it.
Book 30 minutesWho this is for
We say no more often than we say yes. Here is how to tell which one you'll get.
We'd rather lose the deal on the first call than in month three. If the fit isn't there we will tell you on the call and point you at what we'd do instead.
Book the call if
One team owns the work end to end
Finance, revenue or ops. Someone on that team can sit with the engineer a few hours a week. You want to interview the engineer before you sign — you will.
Don't book if
You want headcount or a strategy deck
We don't sell bodies by the hour, we don't write AI roadmaps, and we don't take regulated work. We'll say so on the call and save you the cycle.
What people ask
The questions we get on every first call. Same answers here as you'd get from us live.
If what you need to know isn't here, ask it on the call. We'd rather answer an awkward question early than find it in week six.
How much is it?
It's priced like one senior engineer for a quarter, not like a consulting engagement. Fixed monthly, no hourly billing, no change orders. You get the number on the first call once we've seen the department — the same headline problem is a four-week job at one company and the full twelve at the next, so quoting before we look would be a guess.
What if it doesn't work?
Week 4 is a real exit. We agree the threshold in writing in week 1 and test it against your own past cases before we build anything. If it can't clear, we stop, and you keep the process map and the baseline. We'd rather lose eight weeks of work than ship something your team quietly routes around.
Who is the engineer?
Named in writing before you sign, and you interview them first. They've shipped at Google, General Motors, BAE Systems, Superhuman and Auction.com. One engineer, your department, the whole twelve weeks — not a rotating pool and not a bench you never meet.
How much of our team's time does this take?
One operator for a few hours a week in weeks 1–2, then a review every two weeks. That's it. If nobody on the team can sit with the engineer, don't book — that's the one thing that kills these.
Where does our data live? Do you train on it?
In your accounts, under your permissions, with your SSO. We don't train models on your data and we don't move it into ours. We don't take regulated work.
Our stack is old. NetSuite, spreadsheets and an inbox.
Good — that's where the work actually is. An agent that only runs against a clean modern API isn't worth hiring anyone for. Our engineers have shipped inside enterprise systems that predate most AI companies.
Why not have our own engineers build it?
You can, and in week three they'll get pulled back onto the product roadmap. The other half of this job is deleting steps, which is a conversation your engineers aren't positioned to have with finance. We do nothing else for twelve weeks.
What happens after week twelve?
Nothing switches off. The agent runs in your accounts and your team has been reviewing it every two weeks since week five, so the handover already happened. Most teams keep us on a small monthly retainer for changes. Some take it in house. Either way it's yours.
Do you work in our time zone?
Yes. We've been remote-first for eight years, the engineer works your hours, and we show up in person when the trip is worth it. Embedding is a working relationship, not a set of scheduled calls.
The call
Thirty minutes, one department. If it's not a fit we say so on the call.
Come with a department where the same problem shows up every month, and someone on that team who can spend a few hours a week with an engineer. If neither is true yet, the call won't help.
- You describe one department and what it costs you in time or cycle days.
- We map where the work sits and what we'd delete before automating anything.
- You leave with the shape of the twelve weeks and the number.
Alberto Sadde
CTO and co-founder
Runs the agent practice. Built Lex, the contracts agent Meaningful runs on itself.
Orlando Osorio
CEO and co-founder
Founded Meaningful in 2018. Takes the first call alongside Alberto.
Alberto or Orlando takes the call. No sales engineer, no discovery questionnaire.
Book 30 minutes