Fixed-price integration execution

One broken or manual handoff. Live in 15 business days.

Fixed price. Principal, Integration Engineering — not a bench.

Name the process See the fixed prices

Fixed-price path production

StartName the handoffOne operational path

A / $5,000Diagnostic5 business days

B / $15,000Execution15 business days

ScopeOne named process

DeliveryPrincipal-led

DoneLive plus runbook

The job

A process that still needs a person between two systems — a spreadsheet, a re-key, a wait-for-IT, a rating or booking that dies in the gap.

Name one operational handoff and put that path into production.

Published offer

Two fixed-price steps. One named path.

The Diagnostic establishes access, feasibility, and the written scope. Execution puts one approved deliverable into production.

A / DIAGNOSTIC

Confirm the path before the build.

$5,000 5 business days

One named process and the systems on each side
Access list and AtomSphere read access plus screen-share
Go / no-go decision and a written price for B
No production write access

A is a separate engagement and is not credited against B.

B / EXECUTION

Put one approved deliverable into production.

$15,000 15 business days

Choose one SKU per engagement, not both:

B-Env: Azure Boomi runtime dev/prod pair: Windows single-node or Linux multi-node plus gateway, matching shipped patterns. Done means the runtimes are up and the team can deploy a process.
B-Int: One named integration in production plus a one-page runbook.

Proof

Patterns shipped in production.

No borrowed case studies and no logo wall—just the delivery patterns behind the offer.

Brokerage / TMS path: load rating and carrier bid, book, and search without a person bouncing between systems. ~30% less processing time on work of this type.
Azure runtimes for Boomi: multi-node Linux with a gateway and single-node Windows.
Post-acquisition consolidation at a roughly 900-user 3PL off a decomposed JDE environment.
ConnectWise PSA to Dynamics GP via eOne SmartConnect.
13 Boomi certifications, including Professional DataHub / MDM.

FOR

A buyer who can name the process.

Mid-market companies, roughly 80–800 people: freight brokerage, 3PL, distribution, or a post-close stack collision. Typically a CIO, VP Ops, Director of Applications, or owner-CFO.

NOT FOR

Work that needs a different delivery model.

Fortune 500 RFPs, greenfield iPaaS selection, staff augmentation, unpaid discovery, or work that needs a second senior engineer.

Start asynchronously

Name the handoff that still needs a person.

Share the two systems and what sits idle. Craig will reply in writing.

Name the process