Customers
An SES back office, handed over
A 100-person SES company runs its back office on Perstack: lead intake through matching, proposals, assignment, evaluation, and attrition signals. Fifteen back-office workflows from one definition. The build took two person-weeks. It went live after one month and is still running today.
What was handed over
Fifteen back-office workflows covering the work end to end: lead intake and inbound mail, interviews and their corrections, work logs, skill summaries, matching, proposals and proposal tracking, assignment, evaluation, monthly reports, availability watch, and attrition triage. Fifty-two business concepts, twenty-nine screens, Gmail and Slack, all from one definition.
What the rules hold
Quality rules make the agent ask again instead of writing thin answers, process rules block publish-before-review, and every publish waits for a manager.
What's on the record
Every run sits in the tamper-proof record: who asked, what was checked, what committed, and why.
6months
in production
4,800runs
on record
310runs
went through human approval
27runs
blocked by rule
The last six months of this workflow. Every other run passed the rules.
A run, as the system recorded it
- Workflow
- Engineer skill review
- Status
- Production
- Built in
- two person-weeks
held = asked and continued · blocked = write refused
- 09:14Follow-up askedheld by quality rule
A thin answer hit the quality rule. The agent asked for project scope before touching the sheet.
- 09:22Publish attempt rejectedblocked by process rule
Publishing was requested before review. The write never landed.
- 09:31Approval openedwaiting on manager
The pending change, its reason, and the affected record went to the manager.
- 09:36Commit recordedsealed outside the agent
The approved write was stored with who, what, why, and when.