Four ways to work with us
Which one applies depends on a single question: do you want to own the system, or do you want us to operate it? Everything else follows from that.
A note on naming. Not every recurring fee is an Infrastructure Subscription. A retainer for ongoing improvements is a different thing from operating critical knowledge, retrieval and analytics infrastructure day to day. We use the term only when that is genuinely what is happening — otherwise it is a Monthly Retainer and it is priced like one.
Estimate your engagement in five questions
An indicative range built from the same factors described below. It is a rule of thumb, not a quote — but it is the same rule of thumb we start from.
Who runs the system once it works?
This is the question that decides your engagement model. Everything else only moves the number.
The one question that decides everything
Answer it honestly and the engagement model picks itself.
Technical complexity tiers
These describe the depth of engineering in a system and drive project cost. They do not decide the engagement model — a Tier 2 system can run under either one.
Tier is not the engagement model. Tier describes how deep the engineering goes. The question on this page decides whether you engage through Build plus Retainer or Setup plus Subscription. They are independent choices.
What actually moves the number
There is no price list, because there is no standard project. These six things decide where in the range you land.
Problem Complexity
Novel domains require more research. Well-understood domains require less. The harder the problem, the deeper the investment.
Data Requirements
Do you have clean, labelled data? Do we need to build labelling infrastructure or generate synthetic data? This affects cost significantly.
Custom Architecture
Adapting existing models versus building from scratch. Custom architectures require more research, training cycles and validation.
Integration Complexity
Real-time requirements, edge deployment, existing infrastructure — these all affect implementation scope and ongoing cost.
Domain Expertise
How much do we contribute to problem framing? The less domain knowledge on the client side, the more RebellionTech must provide.
Timeline Flexibility
Urgency has a premium. We do not rush research — but if urgency is required, it is priced accordingly.
No discounts, no surprises. These ranges reflect real cost. Custom intelligence is expensive because it is real engineering work, and we do not compete on price. Once the audit is done, the number we quote is the number you pay.
From first email to running system
Every phase has an exit condition. If a phase cannot clear it, we stop and say so rather than carrying the problem forward into the next one.
Phase 01 stands alone. The architecture audit is a self-contained deliverable. Take the document, build it yourself, or take it to another firm. There is no obligation attached and no pitch at the end.