How a 150-person engineering firm grew without back-office hires.

Three production automations on existing tools (Wrike, Sembly, n8n). ~40 hours of manual work removed per automation. No new hires. The nuclear-sector case in detail.

Liliia KarpenkoOctober 2, 20258 min read

A nuclear energy engineering firm was running critical project operations across two countries — and their back-office was held together by one secretary manually sorting emails, writing meeting notes, and maintaining spreadsheets by hand.

When we mapped the workflows, three things stood out:

1. Email → Wrike, automatically

Every project email had to be classified, numbered, and turned into a Wrike task. We wired the inbox so that every email from a known sender is now classified, logged, and turned into a Wrike task in the correct project folder. The secretary only touches edge cases.

2. Meeting notes that write themselves — in three languages

After every meeting, the recording is picked up automatically. A structured protocol with decisions and action items is generated. Multilingual PDFs are produced. Everything is attached to the right Wrike task.

By the time the team opens Wrike, the notes are already there.

3. Live performance dashboard, monthly

On the 1st of every month, the system pulls task data per employee from Wrike, calculates metrics (completed, overdue, backlog, active hours), and surfaces them in a dashboard with an AI-generated analysis.

Leadership stopped chasing data.

What this didn't include

A fourth automation — auto-tagging project codes from inbound PDFs — is still in PoC at ~70–80% accuracy. We don't ship beta automations as live. It stays in PoC until it crosses the threshold.

The outcome

Each of the three shipped automations removes ~40 hours of weekly manual work. The firm grew without a single new back-office hire.

The systems just keep running. That's the whole point.

See more engagements like this.

11 more cases — operator-honest, paraphrased testimonials, real outcome metrics. Filter by symptom or product.

Browse the cases →