Back to home

Pricing · Scoped to your work

Engagements & investment

One workflow or a connected operation. Agree the result, delivery window and ongoing costs before you commit.

From your workflow to a scoped proposal.

  1. 01 · Discovery

    Bring one workflow.

    Start with the task that slows your team down. Bring the tools and accounts involved, an example of the steps, and the result you want. The first conversation is a 30-minute Discovery Call.

  2. 02 · Scope

    Confirm the scope.

    We agree the workflows, data and access needed, the review points, and the training your team needs. The delivery window starts after the prerequisites are ready.

  3. 03 · Proposal

    Review your proposal.

    Your proposal identifies the implementation work, ownership, delivery window and support plan. Maintenance and third-party costs are separate, so you can review the investment before you commit.

Choose the scope that earns its place.

Prove one workflow, build a full system, or maintain what is already running. Integration depth, data readiness and support coverage shape your proposal.

Tier IMicro Implementation48 hours · Productized · Fixed Scope

Micro Implementation

One clearly scoped workflow, delivered in 48 hours once its scope, account access, and source data are ready. A walkthrough shows your team how to use it. We confirm that your workflow fits before the build starts.

Included in the scope

  • One agreed, fixed-scope workflow
  • Deployed workflow and recorded walkthrough
  • Scope and prerequisites confirmed before the build

What shapes the engagement

  • Agreed workflow and fixed scope
  • Connector and account-access requirements
  • Source-data readiness
View Micro Implementation
Tier IIPilot Implementation7 days · Collaboratively Scoped

Pilot Implementation

One full system, scoped together and shipped in a week. The bridge between a Micro and a Full: substantive enough to prove the model, contained enough to avoid the commitment of a 30-45 day engagement. Pilot fees credit toward a Full Implementation within 30 days.

Included in the scope

  • One production system
  • Collaborative scoping
  • Credits toward a Full if upgraded within 30 days

What shapes the engagement

  • System and integration complexity
  • Data access and security requirements
  • Training and handoff needs
View Pilot Implementation
Tier IIIFull Implementation30-45 days · Multi-Workflow · Core Tier

Full Implementation

Connect the workflows that matter most to your business: customer communication, lead handling, reporting, or operational monitoring. Includes onboarding, training, documentation, and 30 days of post-launch support.

Included in the scope

  • Multi-workflow rebuild
  • Training + documentation
  • 30 days of post-launch support

What shapes the engagement

  • Number and dependency of workflows
  • System and data integration depth
  • Rollout, training, and support requirements
View Full Implementation
Tier IVMaintenanceOngoing · Recurring

Maintenance

Keep deployed systems monitored, patched, and adapted as your business changes. We agree the workflows covered, support expectations, and any planned improvements before the maintenance engagement starts.

Included in the scope

  • Monitoring and patching
  • Support coverage agreed in your proposal
  • Improvements scoped around your needs

What shapes the engagement

  • Number of deployed workflows
  • Monitoring and response coverage
  • Expected change and extension frequency
View Maintenance

Account for the costs after launch.

Your proposal identifies any software subscriptions, hosting, AI usage, and maintenance needed for the agreed system. A Full Implementation includes 30 days of post-launch support. Ongoing maintenance is agreed separately.

Discuss a scoped proposal
Engagements & investment · Kipnetic