COMPARE/Markin vs building it in-house
Markin vs building it in-house: what a team can realistically ship
+17–35% ARPU against holdoutObserved range across Markin deployments, measured on treated cohorts.
An in-house team can build a decision layer: models, feature store, orchestration, experiment framework and activation. The question is throughput. Markin generates, sizes, launches and reads hypotheses continuously, so the same team supervises hundreds of tested ideas per quarter instead of shipping a handful.
The short answerLast updated: August 2026
This is the honest comparison, because the alternative to Markin is usually not another vendor, it is a roadmap. In-house wins on control and on domain judgement. Markin wins on throughput and on time to a verified number, and it makes your team the reviewers rather than the builders.
01
In-house data science and growth
Your own analysts, scientists and engineers building models, pipelines, experiment frameworks and activation on top of the warehouse.
Choose it when the domain is unusual, the team is already staffed for it, and control matters more than speed.
- Full control
- Domain knowledge
- Bounded by headcount
02
Markin
The same operating loop, run continuously by an autonomous system your team supervises: hypothesis, sizing, design, execution, holdout read, scale or retire.
Choose it when the backlog is measured in quarters and the base is large enough that untested ideas are expensive.
- Hundreds of tested ideas
- 90 days to a number
- Your team reviews
Line by line
The same ten questions, answered for both.
| Dimension | Markin | In-house data science and growth |
|---|---|---|
| What it is | An autonomous growth-science team: it investigates why revenue per customer is stuck and acts on what it finds. | A team, a warehouse and a roadmap. |
| What it decides | Which commercial opportunity deserves to exist for each customer this week, what it is worth, and when the right answer is to do nothing. | Whatever the team has had time to build a model and a pipeline for. |
| Where hypotheses come from | Generated by Markin from customer, product, pricing and technical-health data, then sized before anyone builds anything. | Proposed in planning, filtered by seniority and capacity. |
| Scope of action | Marketing, product, pricing and technical-health hypotheses, arbitrated against each other in one queue. | As broad as the team's remit, in practice narrowed to what is shippable this quarter. |
| How the work reaches the customer | Written back into the systems you already run, as attributes, events or API calls. Markin does not add a new customer-facing surface. | Custom integrations built and maintained per channel. |
| How impact is proven | A randomised holdout on every decision. The reported number is incremental revenue and ARPU, not attributed conversions. | Good when the team insists on holdouts; often the first thing dropped under deadline. |
| Where the data sits | Reads context where it already lives, warehouse, CDP, product and billing systems. No new system of record. | Your warehouse, with a feature store to build and maintain. |
| Governance and control | Every action carries its hypothesis, its expected value, its guardrails and its control group, reviewable before launch. | Whatever the team documents. |
| Time to a verified number | One revenue theme, one channel, one holdout: a defensible incremental number inside 90 days. | Typically two to four quarters before the first defensible incremental number. |
| Best fit | Large B2C bases where the constraint is how many good hypotheses get tested, not how many messages get sent. | Unusual domains, strong existing platform teams, control-first organisations. |
What is at stake
A decision layer is not a tool line item. It moves ARPU on the whole base, every month.
Installed base
2.0M
customers at $24 ARPU / month
Addressable revenue
$259.2M
per year, reachable base
Verified ARPU uplift
+17% to +35% ARPU
on treated cohorts, against holdout
What that is worth
$44.1M – $90.7M
incremental revenue per year
Measured on treated cohorts against a randomised holdout, read over a full measurement window rather than the first weeks. Anonymised range across Markin deployments in large B2C bases; your own holdout is the number that decides. The figures above apply that range to the reachable share of the base on this page's assumptions; they are arithmetic, not a forecast for your business.
Run it on your own numbersThe unsolved part
The bottleneck is throughput, not talent
Strong teams do not fail on model quality. They fail because each idea costs weeks of pipeline, integration and stakeholder work, so only the safest ideas get tested and the long tail of smaller, compounding wins is never examined.
- The queue is ordered by who asked, because nothing sizes ideas in money.
- Integration work dominates: the same activation is rebuilt per channel.
- Holdouts are the first casualty of a deadline, so results become arguable.
- Winners are rarely re-read, so decayed models keep running.
Hypothesis space
Everything a human growth scientist would look at.
Most growth problems are not message problems. Markin is not restricted to the campaign surface: if something is holding ARPU back, it is in scope, and it gets tested the same way.
Marketing
The classic surface, but chosen per customer rather than per segment, and always against a holdout.
- Which offer this specific customer is worth making
- Channel and timing chosen per person, not per campaign
- Contact pressure and fatigue arbitrated across every programme
- Win-back economics: who is worth a discount and who is not
Product
Where the customer actually experiences the value, and where most silent revenue loss happens.
- Onboarding steps that lose customers before first value
- A feature with high retention correlation that half the base never discovers
- Paywall and upgrade prompt placement
- In-product surfaces used as a treatment arm, not just email and push
Commercial
Pricing, packaging and the shape of the offer itself, tested rather than argued about.
- Plan and bundle structure by cohort
- Discount depth against margin, not against conversion alone
- Annual versus monthly framing per customer
- Dunning and involuntary churn recovery sequences
Technical health
Anomalies nobody asked it to look for. This is the category no decisioning engine covers.
- A checkout error rate that rose on one device and one region
- Payment failures concentrated in a single issuer or method
- A broken deeplink quietly killing a high-value journey
- Latency or delivery degradation eating conversion before any message does
Think of Markin as a data science and growth team that never sleeps: it investigates, forms hypotheses, ships them into your own stack and proves each one against a control group, at a volume no human team can reach.
Job to be done
The same work, at a different throughput.
Nothing below needs a tool that does not exist. It needs the work to happen continuously instead of once a quarter, and to be proven against a holdout instead of argued about.
| Job to be done | With in-house data science and growth alone | With Markin |
|---|---|---|
| Notice that revenue per customer is drifting in a segment | Someone spots it in a dashboard review, weeks after it started. | Detected as a signal the day the drift clears noise, with the segment already sized. |
| Explain why it is happening | An analyst is pulled off the roadmap for a two-week investigation. | An investigation runs automatically and returns the drivers with their evidence. |
| Come up with hypotheses worth testing | A workshop produces the handful of ideas the room happened to think of. | Hypotheses are written continuously across marketing, product, pricing and technical health. |
| Decide which hypotheses deserve budget | Prioritised by seniority and gut feel, with no size attached. | Each one is sized in revenue and ranked before anything is built. |
| Choose the next best action for one customer | Segment rules and campaign calendars decide, refreshed when someone has time. | Chosen per customer, per moment, against everything else competing for that customer. |
| Actually launch it | A ticket to the lifecycle team, then a slot in next month's calendar. | Executed inside the systems you already run, with no new channel to adopt. |
| Prove it caused the revenue | Reported against non-qualifiers or a global holdout, if at all. | Every decision carries a randomised control group; uplift is read against it. |
| Kill what does not work | Programmes survive because nobody owns retiring them. | Failing to beat control retires the programme automatically. |
| Do all of it again next week | Capacity-bound: four to eight tests a quarter. | Hundreds of hypotheses in flight in parallel, continuously. |
Honest take
What In-house data science and growth does better.
A comparison that only flatters one side is not worth reading. These are the cases where we would tell you to stay where you are.
Domain judgement is yours, not ours
Your team knows which segments are politically untouchable, which margins are wrong in the warehouse and which promise the regulator will not accept. That knowledge is not replaceable, which is why Markin puts humans in the review loop rather than around it.
Control and portability
Building in-house means no vendor dependency, models you can inspect line by line, and a platform that can be repurposed. Those are real advantages and some organisations should pay for them.
Sometimes the first version is enough
If two propensity models and a weekly export move the number, build them. Markin earns its place when the constraint is the twentieth hypothesis, not the second.
Where Markin fits
Not a replacement. A growth-science team on top.
Markin does not replace the team. It multiplies what the team can supervise, and it takes over the parts nobody enjoys: pipelines, sizing, control-group hygiene and retirement.
Your people review
Every hypothesis carries its evidence, its expected value and its guardrails.
Pipelines stop being the job
Activation into existing systems is handled once, not per idea.
Discipline by default
Holdouts and re-reads are structural, not optional.
Evidence standard
Most of this category reports its own lift.
None of the major engagement, CDP or personalisation vendors publishes an independently verified uplift figure for its decisioning product. Where numbers exist, they come from vendor-commissioned studies or single-customer case studies with no disclosed holdout methodology. The most rigorous public research in the category is not flattering to anyone, including us, which is exactly why we build against it.
BCG reports that when organisations adopt rigorous incrementality testing, they typically find 20% to 40% of their active next-best-action programmes deliver marginal to negative lift.
Independent researchBCG, How Measurement Is Evolving in Next-Best Action (2026)The same research flags novelty effects, new programmes show inflated early results, and recommends 8 to 12 weeks before drawing conclusions.
Independent researchBCG, How Measurement Is Evolving in Next-Best Action (2026)Global-holdout, programme-level ROI measurements often overstate impact through halo effects, pull-forward effects and experiment contamination.
Independent researchBCG, How Measurement Is Evolving in Next-Best Action (2026)
How Markin holds itself to it
- Every decision Markin makes carries a control group. Uplift is reported against that holdout, not against the customers who did not qualify.
- Results are read over a full measurement window rather than in the first weeks, so novelty is not mistaken for effect.
- Programmes that fail to beat control are retired automatically. Killing decisions that do not pay is part of the loop, not an annual review.
- The one figure we quote about ourselves is a range, not an average: +17% to +35% ARPU on treated cohorts against a randomised holdout, across Markin deployments in large B2C bases. We publish no industry benchmark, because we could not source one we would be willing to defend. Your holdout is the number that matters.
Time to value
90 days to a number that survived a holdout.
No replatform, no data migration, no rebuild of the channels you already run. If the first cohorts do not beat control, nothing scales and you have lost a quarter, not a roadmap.
Weeks 0–2
Read the context you already have
Markin connects to the data and the channels you run today, in-house data science and growth included. No migration, no replatform, no new source of truth.
Weeks 3–6
First sized opportunities in test
Opportunities are ranked by expected value, treatments are chosen per customer, and the first cohorts go live with a randomised holdout attached.
Weeks 7–12
First verified incremental revenue
Results are read over a full measurement window. What beats control scales; what does not is retired. Nothing scales on a number that has not survived a holdout.
Which one you should pick.
Choose Markin if
- The analysis backlog is longer than the roadmap and growing.
- You want hundreds of sized, tested hypotheses per quarter, not a handful.
- You need a defensible incremental number this quarter.
- Your scientists should be reviewing decisions, not maintaining pipelines.
- Growth questions span marketing, pricing, product and technical health.
Choose building in-house if
- Your domain is unusual enough that generic hypothesis generation would miss.
- You already have a staffed platform team and a working experiment framework.
- Policy requires every model to be owned and inspectable internally.
- The base is small enough that a few well-chosen models cover it.
- There is no appetite for another vendor in the stack this year.
When you don’t need Markin.
- You want a tool your team will operate as a library: Markin runs a loop, not a notebook.
- The base is too small for controlled measurement.
- Data foundations are not yet reliable enough to size opportunities in money.
Questions buyers ask.
Does Markin replace our data science team?
No, and the deployments that work best have strong teams. Markin changes what they spend time on: reviewing sized hypotheses and owning judgement calls instead of building pipelines and chasing integrations.
Could we build this ourselves?
Yes. Most of the components exist. The realistic cost is two to four quarters of platform work before the first defensible incremental number, plus ongoing maintenance of activation and experiment hygiene.
What does in-house do better?
Domain judgement, full control and inspectability of models, and no vendor dependency.
How is throughput actually different?
Markin generates and sizes hypotheses continuously and only escalates the ones that clear a value threshold, so review capacity, not build capacity, becomes the limit.
How is Markin different from the decisioning or AI already inside in-house data science and growth?
A decisioning engine ranks actions a human already defined, inside the campaign surface it was given. Markin forms the hypotheses itself, marketing, product, pricing or a technical anomaly holding growth back, sizes them, executes them inside in-house data science and growth and your product surfaces, and reads each one against a randomised holdout. It behaves like a data science and growth team, not like an optimiser.
Does Markin only test messages and offers?
No. Anything a human growth scientist would investigate is in scope: onboarding friction, feature adoption, pricing and packaging, dunning, and technical health issues such as a checkout error rate or a broken deeplink quietly killing conversion. Marketing is one of four hypothesis domains, not the boundary.
What is the business case for adding Markin on top of in-house data science and growth?
On a large B2C base, a small move in ARPU is a large number in absolute terms, because it applies to the whole installed base every month rather than to a campaign. Across Markin deployments the verified range on treated cohorts is +17% to +35% ARPU against a randomised holdout. The point is not more messages: it is finding the highest-value action per customer, launching it, and proving it against control before it scales.
How long before it pays for itself?
First sized opportunities are in test within six weeks and the first holdout-verified result lands inside 90 days. Payback depends on your base, margin and programme cost, the calculator on this page computes it from your own numbers, after applying the 20% to 40% haircut BCG finds when next-best-action programmes are incrementality-tested.
Related comparisons