Choose how to work with us.

Starting scope

One 60-minute remote session for one issue or workflow. Follow-up implementation is scoped separately.

Starting scope

One department, up to three processes, two discovery sessions, and one findings review.

Starting scope

One candidate use case, one dataset sample, up to two stakeholder sessions, and a readout.

Starting scope

One approved workflow spanning up to three systems, with one architecture review.

Starting scope

One provider, one resource, one sandbox operation, and a written readout.

Starting scope

Initial scoping covers one business unit. Controls and implementation depend on the organization.

Starting scope

One trigger, up to two supported SaaS apps, up to five actions, and one exception notification.

Starting scope

One request type, two sequential approval levels, one reminder rule, and one exception route.

Starting scope

One employee type, one checklist, up to three tools, and a test hire record. Account provisioning is a separate scope.

Starting scope

One recurring document family, up to ten fields, one intake channel, and one destination.

Starting scope

Up to two data sources, eight metrics, one scheduled report, and one delivery channel.

Starting scope

One storefront, one operations queue, up to three rules, and read-only order access.

Starting scope

One team, one approved document collection, one chat surface, and a pilot question set.

Starting scope

One inbox, up to five intent classes, one guidance source, and draft-only output.

Starting scope

One number, one intent family, one transfer path, one language, and no outbound dialing.

Starting scope

One agent, up to three skills, one low-risk approved write operation, and one destination.

Starting scope

One existing assistant, up to 30 approved test cases, and one evaluation round.

Starting scope

Scoping starts with one process and defined agent responsibilities. The production system depends on access and risk.

Starting scope

One team, one CRM pipeline, up to seven stages, and one follow-up rule.

Starting scope

One intake source, one CRM, up to three assignment rules, and one fallback owner.

Starting scope

Two systems, one resource, up to ten mapped fields, and one direction.

Starting scope

Two supported systems, one object type, up to twelve fields, and one conflict queue.

Starting scope

One standard CRM object, up to 5,000 records, up to three cleanup rules, and one batch.

Starting scope

One clean source CRM, one standard object, up to 5,000 records, one rehearsal and one cutover.

Starting scope

One CRM, one billing app, one draft type, and one approval route. Payment actions are out of scope.

Starting scope

One process, up to four roles, one workshop and one map review.

Starting scope

One documented process, up to two teams, one design workshop, and one validation session.

Starting scope

One workspace and up to five existing flows, with read-only inspection.

Starting scope

One existing workflow, one reproducible failure mode, and one regression test set.

Starting scope

Scoping starts with one related flow group. Connector parity and cutover constraints determine price.

Starting scope

One process, up to two data sources, one dashboard, and up to six status indicators.

Starting scope

One six-hour remote workshop for up to 15 attendees using approved client tools.

Starting scope

One workflow group of up to three flows, one written runbook, and one remote handoff session.

Starting scope

One system, up to five workflows, and up to two hours of agreed fixes per month.

Starting scope

One system, up to ten workflows, and up to eight hours per month for approved changes.

Starting scope

Up to two departments and a written monthly capacity plan. Starts after an initial scoping review.