The method · in the open

Diagnose. Blueprint.
Build. Run.

This is the entire way we work, published — because a method you have to buy to see is a hand-off waiting to happen. Ten minutes to read. No black box at the end.

01Diagnose — week one, free

The first call is forty-five minutes with the people who would actually run your project — Matteo and Alessandro, not a sales layer. We ask for three things: access to your numbers, honesty about what hasn't worked, and the outcome you'd write on a wall.

We're filling three baskets before we recommend anything: your present situation and what's less than perfect in it; the prize — the outcome you're actually buying, not the service; and the problems that have stood between the two so far. If we can't fill all three, we don't quote. If we're not the right room, we say so on the call and point you somewhere better.

What you leave with

A straight answer on fit, and — if we proceed — a scheduled date for your blueprint, ten working days out.

02Blueprint — day ten, fixed price, yours

The blueprint is a written document, not a deck. It contains: the scope (what we build and, just as explicitly, what we don't), the architecture (systems, channels, integrations), the creative direction, the team by name, the dates, and one number — the metric the whole engagement answers to — with a fixed price for the build.

Then the part that matters: the blueprint is yours to keep, either way. Build with us, hand it to your internal team, or put it in a drawer. You paid for a plan; you own a plan. This is not a teaser document engineered to be unusable without us — a blueprint that only we can read would just be a hand-off with extra steps.

The worst case

Ten days after a free call, you hold a complete, priced, dated plan you own — and you never pay us again. That's the floor of working with XEPA.

03Build — weekly demos, fixed day

Every week, on the same day, you watch something run: software deployed to a real environment, campaigns live in the actual channel, content published where your market reads. No demo, no invoice — a week where we can't show you working output is a week we don't bill.

04Run — launch is the midpoint

Most engagements die at launch because launch is where the vendor's incentive ends. Ours doesn't: the blueprint named a number, and we review it monthly, together, until it moves. When something underperforms, we say so first and correct it — calmly, with the next iteration already scoped.

Why we can promise this

Because the strategist and the engineer are the same team. When the number stalls, there's no chain of vendors to blame — there's just us, the plan we wrote, and the build we shipped. That alignment is the entire company.

That's the whole method. No proprietary framework with a trademarked acronym, no discovery phase that never ends, no black box. One team, four stops, and a plan you own by day ten.