ENGINE
1 / 12
April 2026
Engine.

An AI intake assistant for engineering services firms.

Why it exists · how it works · what it does for the team.

The problem

Intake the old way.

What goes wrong — and what it actually costs.

Slow first contact
Lost clients. The firm called second never wins.
Inconsistent first impression
Loss of perceived professionalism. The firm looks improvised.
Critical context lives in heads, not systems
Data loss. When someone leaves, the relationship leaves with them.
No structured intake record
No metrics. You can't improve what you can't measure.
Leads land in five different inboxes
Data mixing & overload. Important things drown in noise.
Every partner intakes their way
Ad-hoc workflows. No two leads are recorded the same.
Meet Engine

A chatbot that does the first half of the job for you.

It asks the right questions, finds the right person, and drafts the first response — before anyone picks up the phone.

Lives on the firm's website · available 24/7 · always routes to a real person.

Engine
Thanks for reaching out — what kind of project are you looking to discuss?
Client
Heritage masonry building in Sandy Hill, façade is failing.
Engine
Got it — sounds like building envelope and structural together. How many storeys, and is it tenanted?
How it works

Six steps. Ninety seconds.

01
Visitor lands on the site, chat opens.
02
Engine asks discipline-aware questions.
03
Pulls public client research in the background.
04
Routes to the best-fit team member.
05
Notifies the partner — however they want to be told.
06
Saves the lead — summary, draft email, calendar invite.

All of it before anyone at the firm has read a word.

Capabilities

What it actually does.

Disciplines
Seven covered out of the box — structural, civil, geotechnical, environmental, mechanical, electrical, corporate. Add more in minutes.
Routing
Each lead matched to the best person on the team. Engine can re-route mid-chat as the scope clarifies.
Drafted reply
Every lead arrives with a partner-ready follow-up email already written.
Calendar invite
Generates an invite for the suggested meeting slot — drops straight into Outlook.
Live config
Questions, disciplines, team list, branding — editable in one place. No code, no deploy.
Lead summary
Every lead arrives as a clean, shareable summary — ready for the CRM.
Notifications

However the partner wants to be told.

Ten channels. Pick one, pick all of them.

›Microsoft Teams
›Email
›SMS
›Slack
›System tray pop
›Sound alert
›Priority routing
›Daily digest
›Weekly report
›Stale-lead alert

Each partner picks their own — some want the chime, some want the silent tray pop, some only want the weekly digest.

A day with Engine

Tuesday, 9:42 AM.

9:42
A municipal client lands on the website and opens the chat.
9:46
Engine has scope, location, timeline, budget range, and contact info. Pulls public records on the company.
9:46
Notification to Mike Torres — civil, municipal projects, available.
9:47
Mike opens the lead: summary, fit score, suggested email, calendar invite. All pre-filled.
9:48
Mike edits two sentences, hits send, books the slot. Total time: 90 seconds.

A week of this and the team gets back hours.

Documented & auditable

Every interaction, on the record.

Conversations
Every chat saved end-to-end. No "he-said-she-said" — go back and read the original.
Routing decisions
Every match logged with the reason. Why this person, why now.
Notifications
Every alert stamped — when sent, to whom, on which channel, whether opened.
Configuration
Every change to questions, team list, or branding tracked and reversible.
Replayable
Six-month-old leads reopen with full context, instantly. Search, filter, export.
Compliance-ready
Discoverable, exportable, ready for review without a scramble.

Nothing happens that can't be replayed.

Analytics

The intake desk that finally writes its own report.

Lead volume
By week, month, quarter, discipline. Spot the trends before they become problems.
Response time
Average, median, slowest. Per partner, per channel. The number that decides who wins.
Conversion rate
By discipline, by source, by team member. Where the wins actually come from.
Fit-score distribution
Which leads convert, which don't. The shape of the work that fits the firm.
Partner load
Who's overwhelmed, who's free. Routing tunes itself off this number.
Drop-off insight
Where in the conversation clients lose interest — and what to fix.

All of it from data Engine collects naturally — not bolted on after the fact.

No surprises

It just works.

  • › Cheap to run. Pennies per intake. No license tier, no per-seat fee, no surprise bill.
  • › In-house. Nothing leaves the firm's network. Your data stays your data.
  • › Fully under your control. Turn it on, turn it off, change anything, any time.
  • › Standard tools. Nothing exotic. Anyone comfortable with everyday office software can keep it running.
  • › No special hire. The same person who maintains the website can maintain this.

Quiet, dependable, boring in the best possible way.

What's next

Roadmap.

  • ↗ Voice mode. Speak instead of type — same intake, hands-free.
  • ↗ CRM hand-off. One-click export to whatever the firm already uses.
  • ↗ Custom branding kits. Drop-in colors, logos, voice for any firm.
  • ↗ More disciplines. Architecture, planning, surveying — any practice area.
  • ↗ Multi-office routing. For firms with more than one branch.

All optional. The core is shipping today.

Try it

Engine is ready when you are.

For your team
Open a chat session, watch a lead come through, see the partner notification land. Five minutes, end to end.
To discuss
Embed on your site · branding tweaks · adding disciplines · CRM integration · which partners want which channels.
← → · SCROLL · SPACE · F fullscreen