What we build
Built to fit.Built to keep.
Four shapes of Vulc build, from one agent to a full operation layer. Everything runs on your stack and ships only with your approval. You own all of it. What your business sells changes the details, not the shape.
01 · AI agents
Agents work the queue.You sign the sends.
Support, operations and marketing agents built on your tone and your edge cases. They read the queue, draft the work and prepare every action with full context attached. Anything that touches a customer or moves money stops at an approval gate first. You review in one place and ship with one click.
Approval inbox
Refund request over threshold
Waiting on you
Hi Lisa, you are right, that took too long. The refund of €184 is approved on our side and lands in 2 to 3 working days.
#8391 · support agent · policy: refunds above €150 need sign-off
- 14:31 · reply sent for #8409 · standing approval
- 14:28 · tracking link sent for #8412 · standing approval
approval-first. nothing ships without you.
Typical build
- Support agent on your helpdesk, trained on your real tickets
- Approval inbox: one place to review and sign off
- Escalation rules for the cases that stay human
- Audit log of every draft, decision and send
- Runs in your environment, on your accounts
02 · Dashboards
Every number that matters.On one screen.
One dashboard for the numbers you actually run on, down to true profit per product, service or client after every cost. Data pulls straight from your stack instead of a nightly export. The layout is built around your decisions, so the number you check at 8am is the first thing you see.
Profit dashboard · live
refreshed 5m ago
€8,412
revenue today
€2,180
acquisition spend
31%
net margin
€11.20
profit per sale
net margin, last 7 days
illustrative layout. yours is built around your numbers.
Typical build
- Profit per product, service or client, per channel, per day
- Direct connections to your stack, no exports
- Views per role: owner, ops, marketing
- Alerts when a number crosses your line
- Your data stays in your own accounts
03 · Automations
The busywork, wired.The judgment, yours.
The repeating work between your tools, connected end to end: tagging, routing, follow-ups, reconciliation. Every run is logged, and every step that moves money or emails a customer waits for a yes. When something fails, it fails loudly, with a paper trail.
Flow runs · today
- 09:14 · run #312 · follow-up sequence · 3 drafts prepared
- 09:02 · run #311 · review requests · 14 sent on standing approval
- 08:47 · run #310 · daily reconciliation · clean, no variances
Discount above threshold
#312 · held at the gate, draft ready
Needs your call
approval-first. nothing ships without you.
Typical build
- Flow mapping from your real week, not a template
- Gates wherever money or customers are touched
- Run log with a full audit trail
- Failure alerts that name the exact step
- Handoff documentation for every flow
04 · Full systems
The whole operation.One owned layer.
Agents, dashboards and automations working as one system, with an orchestrator deciding what runs when. This is the shape of the platform we built for ourselves, fitted to your operation instead. It arrives as working software in your environment, with the keys.
Orchestrator · live
- support · queue clear · 2 drafts in your inbox
- email · winback campaign drafting
- ops · inventory sync clean
- reporting · weekly margin report ready
Weekly ad budget shift
prepared by the media agent, context attached
Needs your call
approval-first. nothing ships without you.
Typical build
- Orchestrator plus the specialists your operation needs
- One approval surface across everything
- Runs in your cloud, on your accounts, with your keys
- Documentation and runbooks for the whole system
- Optional retainer to optimize and extend it