Evolve experiences,
don't ship code.
Ekitai orchestrates your digital touchpoints, reads their data and tells you the next move — then applies it. A decision layer with a single goal: moving your organization's metrics up.
Shipping fast
isn't winning.
The market has solved output speed: today a prompt can generate a site. But a fast, blind touchpoint is still a cost. The real question is another one: after launch, do your metrics move?
You launched the touchpoint. Now what?
Page builders and AI prototypers stop at deploy. Nobody tells you whether that page moved a single metric. The work ends where it should begin.
Data lives in one place, decisions in another
Analytics in one tool, the site in another, decisions in a Monday call. No loop links what happens to the next product change.
Every project starts from scratch
The experiment that worked six months ago isn't written down anywhere. The organization doesn't accumulate: it starts over, every time.
Not an assembly line.
A loop that closes.
Other tools take you from brief to touchpoint and stop there. Ekitai watches what happens after launch, decides the next move and applies it to the touchpoints themselves. The result improves your metrics, not your changelog.
Ekitai Sprint.
€10,000. Five days.
Five days to take an idea from brief to a live experience on Ekitai. Every session ships something publishable. At the end you have a live touchpoint and its control room switched on: the first measurable movement of your metrics, not just the first output. If it doesn't get off the ground, you get everything back.
Three layers,
one single loop.
Orchestrating touchpoints is the starting point. Measuring them is the bare minimum. Deciding and evolving them automatically toward your metrics — that's Ekitai.
One brand, every touchpoint
Onboarding in 30 seconds: color, font, logo. Atomic design at the core. Web, app, e-commerce, DOOH and spatial are born coherent from the same source.
One control room, not ten reports
KPIs, activity, pain & gain over time, for every surface. Your customers' real behaviors in one place — without pasting dashboards into slides.
The layer that tells you the next move
The engine reads the data, proposes recommendations and A/B tests, and applies the change directly to your touchpoints. Continuous Design, in production.
Everyone stops at launch.
Ekitai starts there.
Excellent up to launch
Webflow, Framer. They make beautiful sites, and they make them fast. Then they stop at deploy: nobody tells you whether that page moved a metric.
Very fast, then redone
Lovable, v0, Bolt, Figma Make. Prototypes in thirty minutes. Then a senior dev spends two weeks making them accessible and deployable.
Flexible and laborious
Figma plus seven tools. Flexible — everything is possible, by hand. The data sits in one place and the decisions in another.
The decision layer
It reads the data after launch, recommends the next move with an estimated impact, and applies it to the source. It's the only one that closes the loop toward the metrics.
Twenty years of digital product.
Distilled into a loop.
Ekitai doesn't come from a thesis about how design systems ought to work. It comes from twenty years of shipping them into production and watching them hold — or give way.
€360k
saved across nine years in production: the design system stopped being a project to redo and started compounding value with every cycle.
11
coherent digital products from a single design system, with no rebrand endured and no reset.
20 years
Carlo Frinolli has shipped design systems into production at Airbnb, Coca-Cola, Microsoft, Mozilla, Philips, Poste Italiane and Accredia.
5 live touchpoints
carlofrinolli.it, ASD Tennis Time, FederCUSI · Monban, WUDRome, noiz.be. FederCUSI uses Ekitai for the Monban federated login; WUDRome for its annual UX event site.
A touchpoint isn't launched.
It's grown.
Digital touchpoints aren't finished products. They're living manifestations of your value proposition, and they must be measured and moved toward your metrics. Continuous Delivery is technique. Continuous Design is strategy.
The questions
you don't expect from marketing.
Missing yours? Write to us and we'll add it.
Does Ekitai replace Webflow or Framer?
No. Webflow and Framer are excellent visual page builders and they stop at the site. Ekitai is a decision layer above your touchpoints: it orchestrates them from one brand source, reads their data and evolves them toward the metrics. If you only need a brochure site, Webflow is enough.
How does it actually improve my metrics?
By closing the loop. Touchpoints built in Ekitai emit data; the decision layer reads it, ties it to movements in acquisition, conversion and retention, and proposes the next move with an estimated impact. You approve, apply, measure. Every cycle leaves reusable knowledge behind.
What happens if I want to leave Ekitai?
You export. The stack is Next.js, Strapi and PostgreSQL on Vercel — standard, readable, yours. No proprietary format. If you decide to run it in-house, take the repo and carry on without us.
Does it work with my existing brand?
Yes. Paste your colours, fonts and logo into the onboarding panel and you have a theme in thirty seconds. If you already have a structured design system you import it; if you don't, we build it during the Sprint.
And the real difference with Lovable, v0, Bolt?
They generate prototypes: code to refine, to make accessible, to deploy. Ekitai generates production-ready experiences: WCAG 2.1 AA, SEO, GDPR, ISR, multi-tenant. Their output is a starting point; ours is something your customer uses on Monday morning.
What's the price after the Sprint?
Pricing linear to the brand: you pay per instance — one brand, one source — not per touchpoint and not per visit. After the Sprint you can continue on a monthly fee or leave, with no contractual lock-in.