FIORIANALYTICS

How the partnership works

I work behind your agency, not next to it.

White-label means the technical work is mine and everything the client sees is yours: the brand on the report, the voice in the meeting, the relationship. This page lays out the whole arrangement. What I do, what stays yours, what I need from you, and what it costs.

Book a 20-min partner call Or send one client site for a free teardown →
Daniel Vieira, founder of Fiori Analytics

Daniel Vieira, founder of Fiori Analytics. The call is with me, and so is the build.

Four steps, and you stay in front of the client for all of them.

01

You bring the client.

I scope the job with you. Your client doesn't have to be in that conversation, and usually isn't. You decide how much of it I'm in.

02

NDA, then read access to what the job needs.

Signed before anything is shared. Access is scoped to the systems the build touches: the ad accounts read-only, the tag manager, and whatever holds the leads.

03

I build it, document it, and QA it against real data.

Every event is checked against the source system before anything is called done. You get the documentation as part of the delivery, not on request.

04

You present it as your work.

Reports and documentation carry your name. The client keeps everything we set up, inside their own accounts.

What stays yours

  • The client relationship. I don't contact your client unless you put me on a call.
  • The branding. Reports and documentation go out with your logo. Mine is not on them.
  • The account. Everything is built inside the client's own ad accounts, tag manager and cloud project.
  • The margin. You're quoted a fixed price per project. What you charge on top is your business.

What you receive

  • A written report in your agency's branding, ready to hand to the client
  • Technical documentation: what was built, where it lives, and how to change it
  • A recorded walkthrough you can forward or present yourself
  • A QA record: every conversion checked against the client's own system
  • A handover call with your team, so nothing depends on me afterwards

What I need from you

  • Read access to the ad accounts and the tag manager, after the NDA
  • One technical contact who can grant access, on your side or the client's
  • The list of outcomes the client actually cares about (booked consult, signed case, sold unit)
  • A realistic date. Rush jobs are the ones that break QA

Pricing

Fixed price per client project, quoted before any work starts. Partner pricing is built so you can mark it up.

You don't need a retainer to start, and nothing is priced by the hour. You need a number you can put in your own proposal before you talk to the client.

Confidentiality

  • NDA before access. Signed before anything is shared, plus a DPA when the client's legal team asks for one.
  • Your client's data stays put. It never trains anything, never lands in a benchmark, and never gets shown to another agency.
  • Findings stay inside the engagement. What I see in your client's account does not travel to another account.
  • No going around you. I never contact a client you introduce to me unless you ask, and I don't use anything from your projects to approach them.

Questions partners ask

What does white-label mean here?
I do the engineering. Your agency owns the client relationship, the branding and the presentation. Reports and documentation go out with your name. I only talk to your client if you want me on a call.
Do you work with more than one agency in the same city?
Yes. I don't take exclusivity, and I don't need to know who your competitors are. What I won't do is move a build, a report or a finding from one agency to another.
Who owns what we build?
The client does. It's all built inside accounts they already own: their Google Ads, their Meta Business Manager, their tag manager, their cloud project. If you stop working with me, nothing switches off.
How is it priced?
Fixed price per client project, quoted before any work starts. Partner pricing is built so you can mark it up.
How long does a typical setup take?
Every project is scoped first. You get the timeline in writing with the quote, before any work starts.
Do you need access to the ad accounts?
Not for the teardown. That one runs from the outside, with no logins. For the build I need read access, plus whatever specific permissions the job calls for, after an NDA.

Send me one client domain. I'll show you where the trail breaks.

No access, no logins. A read-only teardown, delivered without Fiori branding so you can present it as yours.

Get a free teardown