Pricing and Engagement
A defined scope and a clear investment.
Your first engagement is priced around the operation we agree to improve. You see the implementation, ongoing management and any added software costs before you commit.
- Implementation: we build, connect and test the operation
- Ongoing management: we run it, review it and improve it
- Third-party software or usage costs named up front
Two Parts
Implementation builds it, and management keeps it improving.We build it, then keep it improving.
A system built and then left alone drifts as your business changes. That is why every engagement has two parts, and you see both before you commit.
Implementation
- Understand the work and set the baseline
- Agree the actions and approvals
- Connect your existing software
- Build and test before launch
- Launch alongside your team
Ongoing management
- Monitor the work and route exceptions
- Investigate failures and maintain sources
- Review results with you every week
- Improve under your team’s oversight
- A named contact at Struq
Verified client result
$336K annual contribution improvement for an $18M ecommerce brand, before Struq’s fee and added system costs.
What Affects Scope
Six things in your operation set the scope.
Scope follows six things we can see in your operation, and we review each one with you before suggesting an investment.
Systems involved
How many software systems the work touches and how they connect today.
Information readiness
Whether the records the work depends on are current, complete and reachable.
Volume
How much work moves through the operation each week and how unevenly it arrives.
Exception complexity
How often cases leave the normal path and how much judgment they need.
Coverage
The hours, channels and locations the operation needs to cover for your customers.
Required approvals
Which actions your team must approve before anything goes out on your behalf.
Where It Starts
Know where to start after one conversation.
The first conversation identifies a practical starting point. Where the requirements are clear, we can discuss the likely scope and investment. We confirm the implementation details and responsibilities before work begins.
- The operation most worth improving first
- What waiting is costing you now
- What we’d need to see in your systems
- Where your team keeps the decisions
- The likely scope, where requirements are clear
- A clear next step for both sides
Booking the conversation commits you to nothing.
One Operation First
Start with one measurable problem and expand only after proof.
The first operation earns the next one. Each expansion is scoped the same way, from results you have already seen.
- Step 1
Find
Review real cases and set a baseline.
- Step 2
Build
Agree actions and approvals, then test.
- Step 3
Run
Run it and route exceptions.
- Step 4
Improve
Review results and plan the next step.
Common Questions
Questions about how the engagement works.
Who runs it day to day?
Struq does. A named contact monitors the work, handles exceptions and reviews results with you every week.
What happens if the agreed outcome hasn’t arrived by day 60?
If the agreed outcome hasn’t arrived by day 60, we keep working at no additional cost until it has.
Are there other costs to plan for?
Some operations rely on third-party software or usage-based services that carry their own charges. Any of those costs are identified before you commit.
Why is there no price on the website?
The investment depends on your systems, volume, exceptions and approvals, so a single published figure would be wrong for most businesses that read it.
What does our team provide?
Access to the systems involved, knowledge of how the work runs today, the decisions only your team can make and feedback on results.
Start Here
Start where the work costs you most today.
If the agreed outcome hasn’t arrived by day 60, we keep working at no additional cost until it has.