How we work together
Working with Fidero splits three ways: we bring the judgement, your engineers own your code, and the platform runs the operations. In one line: expert-led setup, customer-owned deployment, platform-run operations.
This page covers what that means in practice, including the question you may already be asking: there’s no self-serve dashboard today.
Who does what
Section titled “Who does what”| The work | What it covers | Who owns it |
|---|---|---|
| Judgement | The audit, journey mapping, identity strategy, implementation tickets and QA checks | We do – at setup, and whenever your stack changes |
| Implementation | Instrumenting events in your code, then review, merge and deploy | Your engineers |
| Operations | Enrichment, identity resolution, delivery, adapter updates, config and monitoring | Fidero, continuously |
The boundary holds through the whole relationship. Where it’s faster, we’ll draft a change as a PR – you still review, merge and deploy it. Your application code never leaves your hands, and you never have to operate the runtime.
There’s no dashboard today
Section titled “There’s no dashboard today”Configuration lives on the server, and it’s deliberately small: which destinations are on, their credentials and the occasional override. How each event is mapped, formatted and deduplicated for each tool lives in platform code, not in settings you’d reach through a console. A dashboard would give you very little to do.
What the model gives you instead:
- One config governs the SDK and the server, so client and server can’t drift apart
- Changes land without a release – configuration is pulled at runtime, not baked into a deploy
- We keep the adapters current – when a tool changes its API, the fix reaches you with zero action
- Delivery is monitored, and a failing integration raises an alert
Requesting changes
Section titled “Requesting changes”Requests travel over email, Slack or a shared configuration repository – whichever you already use with us. You state the outcome – “Send abandoned-cart events to Klaviyo” – and your configuration updates on the server within 24 hours. Nothing redeploys on your side.
Destinations covers enabling a new tool, and Configuration & changes covers the request flow in detail.
What stays yours
Section titled “What stays yours”Your code and your data. Every change to your application is implemented, approved and deployed by your team – we supply the tickets, the specs and sometimes a PR, never the deploy. And Fidero delivers the enriched data to your tools and your own warehouse, so the data asset builds up in infrastructure you own. If you ever leave, it stays where it already is.
Data ownership & portability covers the detail.
How an engagement starts
Section titled “How an engagement starts”Every engagement starts with a Data Infrastructure Audit: a paid, focused diagnosis of where your data breaks, with evidence from your own destinations. What follows is a 30-day implementation sprint with your engineers, and then the platform runs. Onboarding covers what provisioning looks like step by step.