Let's talk.
A 30-minute call. We listen, frame the problem in your vocabulary, and tell you whether this is something we should build for you. If it is not, we will tell you what kind of firm would be a better starting point.
What the call looks like
- 30 minutes. 15 if your situation is well-defined enough that the longer slot is not needed.
- We listen first. You tell us what is happening. We will not pitch in the first ten minutes.
- Then I frame the problem back in your vocabulary. This is the moment that tells you whether we understand the work. If we do not, the rest of the call is correction. If we do, the rest is sizing.
- You leave with a clear answer. Either yes, we should keep talking, or no, you need a different kind of firm. We will tell you which kind, and where to find one.
- If yes: within 48 hours, a written summary of what you said and a proposed Phase 1 scope.
- If no: within 48 hours, an email naming what kind of firm would be a better fit and, where I can, two or three specific firms worth reaching out to.
No follow-up sequences. No mailing list. The scoping call is the entire pre-engagement motion.
Book directly
Calendar below. If the times shown do not fit, send a note through the form and we will find a slot.
Or write
If you would rather write than schedule, the form below sends a message to hello@trestlegroup.com. We respond within two working days.
Or take the assessment first
If you would rather get a structured read on where your operations stand before a call, the 5-minute self-assessment is the entry point.
Eighteen questions across six dimensions of operational maturity. Results display instantly. A copy by email if you want it.
Start the assessment→Or just email
We respond within two working days. If we are at capacity and cannot take on new engagements, we will say so directly and refer you to a firm that can.
Logistics
- Time zones. Scoping calls available across US Eastern, US Pacific, and Western European hours. Other zones by arrangement.
- Languages. Engagements run in English.
- NDAs. We sign a mutual NDA before any conversation that touches specific data, financials, or proprietary workflows. If you have a standard NDA, send it ahead of the call.
- References. Available on request once a scoping call confirms initial fit. Reference contacts are former clients who have agreed to take occasional calls. Out of respect for their time, we do not share their names speculatively.
No sample data before the scoping call. No budget. Nothing to sign. No executive sponsorship required before we talk. The first contact is low-cost on your side by design. The friction starts once we have confirmed there is something to build together.
Questions we hear before the first call.
Is my data safe with you?
We sign a mutual NDA before any conversation that touches specific data. During an engagement, we operate on your infrastructure or in an isolated environment you control. We do not retain client data after handoff. The agent reads your data; it does not export it.
What happens if the AI makes a wrong call?
It will, and the architecture accounts for that. The AI layer is sandboxed to reading and classifying. It does not approve, delete, or modify records. When it gets something wrong, the result is a flag in the review queue with the wrong classification, not a corrupted ledger or an unauthorized transaction. Your team catches it in the same queue they would catch any other exception.
Does this work with our existing systems?
The agent reads from your existing systems. It does not replace your ERP, your accounting software, or your document management platform. It sits alongside them. If your data is accessible via an API, a database connection, or an export, the agent can work with it. We have built agents that read from NetSuite, QuickBooks, Sage, Google Workspace, SharePoint, and custom internal platforms.
What happens after the engagement ends?
You own the agent. The rule catalog, the pipeline code, and the documentation are yours. We hand off with a production gap list (what would need to change for full unattended operation), a limitations page (what the agent does not handle), and a 30-day stabilization window. After that, you can operate independently or retain us for support.
We tried automation before and it failed. Why is this different?
Most automation projects fail for one of three reasons: they automate a broken process (garbage in, garbage out), they try to do too much at once, or nobody maintains them after launch. We address all three. We streamline the workflow before automating it. We scope to a single workflow per phase. And we build versioned rule catalogs that your team can update without a software deployment.
Do we need technical staff on our side?
Not during the build. We need a business owner who knows the workflow, access to the source systems, and historical data to validate against. After handoff, someone on your team needs to own the review queue and the rule catalog. That person does not need to be technical. The rule catalog is a config file with plain-language descriptions, not code.