Productized packages

MAP → PILOT → RUN → EXPAND

Clear scope boundaries for evaluation. Final commercial terms are issued after qualification. Figures on this page are not a public price list.

Fit, security, ownership and when not to buy

The contract still sets the exact terms.

Will this work with our existing software?

Usually yes when mail, ERP, documents, CRM or APIs can trigger or receive the step. Compatibility is confirmed in the map. Complex custom APIs are scoped separately.

How complex is a typical pilot?

One trigger, up to two integrations, one human approval stage, agreed exceptions, test evidence and handover — typically a few weeks after access is confirmed.

How is pricing set?

The map is free for accepted briefs. Pilots, RUN support and EXPAND work are quoted after qualification. This page does not publish a public price list; commercial figures require internal approval before commitment.

How is data secured?

We use least access needed for the step, prefer your accounts, and document who can pause the flow. Credentials are not collected in this form. Details are written in the engagement agreement.

Where do human approvals stay?

Money, compliance and commitments stay behind a named gate. Automation moves certain work and records who decided the rest.

Who maintains it and who owns it?

You own the process and data in your systems. RUN defines monitored workflows, hours and exclusions. Deliverables and any code ownership are stated in the contract. We do not claim unlimited support or guaranteed uptime.

When should we not buy this?

If a simple DIY zap already works safely, if there is no repeated step, if systems cannot be accessed for a pilot, or if you need a full ERP rebuild — see Enterprise applications or AI workflow instead.

Qualified enquiry

Get a free workflow map

Describe one repeated step. We triage briefly. Accepted briefs receive a one-page map. Unfit briefs may be declined. Your submission creates a New lead — not an automatic Qualified opportunity.