Home / Stack map
How Stradem sits on top of your stack
Your customer data platform, data lake and other systems hold the data. Stradem takes it in and returns the customer groups worth activating first, test plans, value estimates and approved briefs for your team to build. Each layer also shows where it performs best and what to change.
Your data
Bring the data you already have
Data that is ready to activate
Your customer data platform, data lake or warehouse already holds it. Stradem works from the counts, costs and outcomes in them.
A small set is enough to start
One audience, one journey or one channel supports a first comparison and test.
Each result shows what to improve
The comparison shows which data gaps to close first. Your stack improves with each decision.
The stack, layer by layer
What Stradem receives, returns and where each layer performs best
Choose a layer to see what moves in each direction, how it moves and where to optimize. Each layer has one named owner on your side.
Choose a layer of your stack
Customer data
Typical systems in this layer
- Data warehouses
- Customer data platforms
- CRM
- Stradem receives
- Aggregate counts of accounts by segment, with usage, order and renewal measures.
- Stradem returns
- Eligibility rules and segment definitions for your team to build.
- How it moves
- Agreed aggregate tables or files on a set schedule.
- Your team keeps
- Customer-level records, eligibility and assignment stay in your systems under your data team's control.
- Where to optimize
- Which audiences are large enough to act on, and which data gaps to close first.
Analytics and measurement
Typical systems in this layer
- Web and product analytics
- Attribution
- Reporting
- Stradem receives
- Engagement, funnel and outcome totals by group and period.
- Stradem returns
- The metric definition, the comparison group and the results date.
- How it moves
- Agreed reports, or read-only access to your reporting layer.
- Your team keeps
- Your analysts own the reporting stack and the definitions in it.
- Where to optimize
- Where reporting separates a tested gain from a forecast, and which metric definitions to tighten.
Activation and engagement
Typical systems in this layer
- Email and lifecycle
- Advertising
- Personalization
- Journey orchestration
- Sales engagement
- Stradem receives
- What ran, for which group, in which period and at what cost, as totals.
- Stradem returns
- The approved brief: audience rules, timing and the offer, for your platform owner to build.
- How it moves
- The brief goes to your platform owner. Totals return by report or export.
- Your team keeps
- Your platform owners run delivery and assignment in the tools they know.
- Where to optimize
- Which journeys and channels return the most per dollar, and where spend can move to them.
Experimentation
Typical systems in this layer
- Testing tools
- Feature management
- Stradem receives
- Group sizes and outcome totals by test arm.
- Stradem returns
- The test plan, the sample size and the result that triggers action.
- How it moves
- The test plan goes over as a document. Results return as totals by arm.
- Your team keeps
- Your test platform runs assignment and exposure.
- Where to optimize
- Which tests are worth the most, and where a faster test cycle pays back.
Models and AI
Typical systems in this layer
- Predictive models
- Propensity scores
- AI services
- Stradem receives
- Score bands and the performance of each band.
- Stradem returns
- Where to apply the scores and what each application was worth.
- How it moves
- Score band summaries by export.
- Your team keeps
- Your data science team owns the models.
- Where to optimize
- Where a score adds the most revenue, and which model needs a fresher input.
Finance and planning
Typical systems in this layer
- Planning
- Budgeting
- Margin reporting
- Stradem receives
- Margin, cost and budget by program.
- Stradem returns
- Decision logs and the value realized, ready for review.
- How it moves
- Agreed tables or a recurring report.
- Your team keeps
- Finance owns the numbers of record.
- Where to optimize
- Which programs earn their cost, and where budget can move to a stronger return.
Connection matrix
How data and decisions move, by layer
Agreed files and briefs are the usual start. Read-only connections and direct connectors are scoped with each platform owner.
| Layer | Agreed aggregate files | Read-only connection | Brief or specification | Direct connector |
|---|---|---|---|---|
| Customer data | Typical start | On request | Typical start | Not typical |
| Analytics and measurement | Typical start | On request | Typical start | Not typical |
| Activation and engagement | Typical start | On request | Typical start | Scoped per engagement |
| Experimentation | Typical start | On request | Typical start | Scoped per engagement |
| Models and AI | Typical start | Not typical | Typical start | Not typical |
| Finance and planning | Typical start | On request | Typical start | Not typical |
- Typical start
- The method most engagements begin with.
- On request
- Set up when the owner of the system approves access.
- Scoped per engagement
- Scoped with the platform owner and listed in the agreement.
- Not typical
- Stradem uses another method for this layer.
Data boundary
What stays in your systems and what Stradem processes
Stradem works with aggregate data only: counts, rates and totals by group and period. Customer-level records stay in your systems.
| Data or work | Where it lives | Role of Stradem |
|---|---|---|
| Customer-level records, identity and profiles | Your customer systems | Stays with your data team |
| Eligibility and assignment of individual customers | Your platforms | Sends the audience rules and the test plan. Your platform applies them. |
| Aggregate data on segments, costs and outcomes | Shared on an agreed schedule | Processes it in the workspace to value opportunities and measure results |
| Decision logs, assumptions and results | Your Stradem workspace | Keeps the record. Your team accesses and exports it. |
| AI-prepared drafts | Your Stradem workspace | Prepares drafts from aggregate data and model results. A person approves each one. |
Questions about the stack
Does Stradem replace our customer data platform, data lake or marketing platforms?
Stradem sits on top of them and uses the data they hold. Your platforms stay in place, and your team keeps running them.
What if we have a small or partial data set?
Start with what you have. One audience, one journey or one channel is enough for a first comparison and test. Stradem shows which data gaps to close first, and the comparison grows as your data does.
Which products does Stradem connect to?
Most engagements start with agreed aggregate files, which any product that can export a table or a report can produce. Read-only connections and direct connectors are scoped with each platform owner.
Where does Stradem fit with our consulting and platform partners?
Stradem compares options across your stack. Your partners keep delivering, and the workspace records what each investment produced.
Where does our data live?
Customer-level records stay in your systems under your data team. Stradem receives agreed aggregate data on segments, costs and outcomes. See how Stradem handles data.