Our own firm
The system Luxin runs its own company on.
The system Marc demos in every meeting: agents draft the briefs, notes and follow-ups for his own company, and he approves every send.
- Status
Built, handed over, and running in the business today.
- When
- Running every working day since July 2026
- Works inside
- Claude Code · Obsidian · Granola · Gmail · Outlook · Google Calendar · Resend · GitHub
What was happening before.
Luxin, an AI consulting firm, built, is building, or proposed this work. The status above says which.
One founder, several leads in motion, a dozen open loops, and no assistant.
Every proposal, follow-up and meeting note lived in someone’s head or a chat window.
The risk every client asks about first: an agent sending something it should not.
The numbers, with what they mean.
- 50+
- daily briefs built by the system since 20 July 2026
- What was built
- 35+
- meetings filed from transcripts into notes and people files
- What was built
- $25
- the spend cap no agent may pass without a person’s approval
- What was built
Every figure says where it came from. A problem found is not a result.
What was built.
- 01
A written constitution that says what agents may do alone, what needs Marc’s approval, and what they must never do.
- 02
A morning brief around 6am and an evening review, built by a chief-of-staff routine from the calendar, the inbox and the meeting notes.
- 03
Meeting transcripts filed into notes, people files and a pipeline register the same day.
- 04
An approval queue: nothing client-facing sends until Marc marks it approved, and a gate blocks anything that tries.
- 05
Every price quoted, every lead and every project in one register, one file per project.
The tools it works inside.
Nothing goes out without you.
The same rule Luxin sells. The system drafts, Marc approves. Client-facing email cannot leave without his word, and a ledger records every time it did.
Where it stands today.
This is the system every client meeting is demoed from. It has run every working day since July 2026, and it is where the firm’s own pipeline, notes and approvals live.
More case studies.
Bender Engineering
Read what happened: Bender EngineeringA San Jose law firm
Read what happened: A San Jose law firmA 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.