Bender Engineering · Engineering
A proposal agent that files the job and drafts the proposal before anyone opens the email.
A proposal agent that turns an inbound request and a set of plans into a filed job and a drafted proposal, ready for review.
- Status
Built, handed over, and running in the business today.
- When
- First version built summer 2026 · second version in progress
- Works inside
- Outlook · SharePoint · Word · n8n · Claude
What was happening before.
Luxin, an AI consulting firm, built, is building, or proposed this work. The status above says which.
Every proposal request arrived as an email with plans attached, and every one was typed up by hand.
A tracking sheet, a client folder, a job folder, a Word template and a terms document, filled in one at a time.
Seven proposals could sit in the queue waiting for someone to have a free afternoon.
The numbers, with what they mean.
- About 6 hours
- a week of proposal-writing time given back, Marc’s own estimate as published on his earlier portfolio site, not a measurement
- The result, as reported
- 7
- proposals sitting in the queue on one day during the build, from the build record
- The problem found
- 4
- documents filled in by hand for every proposal: sheet, folder, template, terms, from the build record
- The problem found
Every figure says where it came from. A problem found is not a result.
What was built.
- 01
The agent watches the proposals inbox and reads each request and its attached plans.
- 02
It adds the job to the firm’s tracking sheet and creates the client and job folders where the team already looks.
- 03
It drafts the proposal from the firm’s own Word templates, using past proposals for that client as precedent.
- 04
A first version ran on a private server; a second version, rebuilt in Claude Code, is in progress. A person reviews every draft, and the owner sends it himself.
- 05
The whole team was walked through using Claude on the firm’s own Microsoft 365, so they can extend what was built.
The tools it works inside.
Nothing goes out without you.
The agent files and drafts. It never sends. Every proposal is read by a person, and the owner emails it to the client himself.
Where it stands today.
The first version ran in the firm on a private server, and the team was trained on Claude on their own Microsoft 365. A second version is being rebuilt in Claude Code. A request arrives, the folders and the tracking sheet fill themselves in, and a drafted proposal waits for a person to review before the owner sends it.
In the owner’s words.
“Really impressive work! From the first call I had with Marc, I could tell I was working with someone who knows what he’s doing.”
More case studies.
A San Jose law firm
Read what happened: A San Jose law firmThe operating system Luxin runs on
Read how it runs: The operating system Luxin runs onA sales team scaling outbound
Read what was built: A sales team scaling outbound
Tell me what’s eating the most time.
Thirty minutes, no deck. You describe how the work actually happens, and I tell you plainly whether there is something worth building.