Rescue, scope, cost, who does the work, and what you keep after we leave.
- Our implementation is late. Can you take it over mid-flight?
- Yes — that is most of our work. We start by tracing recent quotes back to the rules and data that caused the failures, so you get a written read on what is actually broken before anyone touches configuration. Sometimes the existing build is recoverable and the scope was wrong. We say so when that is the case.
- How do you determine whether we need rescue, redesign, or extra capacity?
- A 30-minute program review first. We look at where delivery is breaking: product structure, pricing authority, approvals, data, integrations, or release discipline. If those decisions are still open, adding hours will increase rework. You decide the next step after that call.
- What does an engagement cost?
- We publish our rates and bill weekly or monthly with a 10-hour minimum: administrators $100/hr, developers $170/hr, architects $250/hr. Most programs run architect-heavy for the first few weeks of design, then shift to developers for the build and an admin for configuration. No long-term contract is required.
- Who does the work after the first call?
- Senior administrators, developers, and architects assigned to the program. Discovery leads stay involved through delivery. We do not hand the work to a junior bench after the first call.
- What happens when you leave?
- Your team runs the system. We document configuration and custom logic as we build it, train reps, admins, and developers on your specific setup, and leave runbooks for the routine work. A straightforward implementation typically reaches go-live in 8 to 12 weeks; complex catalogs, multi-currency pricing, or ERP integration usually take 4 to 6 months. We say which one you have during the review.