Florentin Purcea
ROENAnalyse my businessAnalyse

05 Proof · Work

Proof before promise.
Delivered, observed, attributed. Never mixed.

Every claim on this site has an artefact behind it: a URL, a test, a reconciled number. If it cannot be verified, it is not here.

  • Deliveredbuilt and shipped; you can check it.
  • Observedmeasured after shipping; I do not claim the cause.
  • Attributedthe cause is claimed — always with a caveat.

Filter by your problem

8 proofs

Performance marketing agency — 12 client accountsLive

A multi-agent advertising operating system

  1. Issue detected~1,900 recorded leads in one month — far above what the sales team was seeing.
  2. Verification~180 actual leads once form submissions were reconciled against the CRM.
  3. Root causeThe lead event fired on cookie acceptance, not on form submit. Bidding had learned to buy consent clicks.
  4. FixTracking architecture corrected: trigger rebuilt, conversion action remapped, weekly read-only check added so it cannot silently break again.
  5. Measured Delivered~1,900 → ~180 real leadswindow: one month, reconciled · Volume fell because the fake events stopped; bidding re-learned in 9 days.
Open the proof →

Dental clinic, BucharestBuilt, awaiting client go

A dental clinic conversion system with an AI concierge

  1. Issue detectedA live site with an LCP of 11.9 seconds, no booking flow, and calls missed after hours.
  2. VerificationLighthouse on the production URL, call logs by hour, and a walk through the ad-to-appointment path.
  3. Root causeA WordPress theme loading everything everywhere, and a business with no digital front desk after 19:00.
  4. Fix40-page rebuild with a treatment navigator, 3-step booking, an AI concierge with medical guardrails and a server-side emergency gate, plus a zero-loss URL map.
  5. Measured DeliveredLCP 11.9 s → Lighthouse 93 / 100 / 100 / 100window: staging, 30 end-to-end tests green · Built, awaiting the client's go for production; conversion impact not yet observed.
Open the proof →

Towing & roadside assistance, Bucharest — remorcari-tractari.roLive

A phone-first emergency service platform, live

  1. Issue detectedA slow WordPress site for people stranded at night with one hand free — and 207 URLs of SEO history that could not be lost.
  2. VerificationFull crawl of the legacy site, Search Console export, every URL classified: keep, redirect or retire.
  3. Root causeNothing was built for the moment of need: no one-tap call, no WhatsApp, heavy pages.
  4. FixStatic-fast rebuild for one-tap calling and WhatsApp, 30 pages, GA4 with Consent Mode v2, a validated redirect map, staging first and production only with the owner's go.
  5. Measured Delivered207 URLs kept — none lost · Lighthouse 100 × 4window: live in production since 2026-08-30 · Traffic and call outcomes are the owner's data; not published here.
Open the proof →

Agency product, piloted on a dental clinicBuilt, awaiting client go

An AI-search visibility operating system

  1. Issue detectedNobody could say, with numbers, how AI assistants describe the brand — or whether a content change moved anything.
  2. VerificationAI engines sampled through official APIs; every rate reported with its sample size and a Wilson interval; brand-truth facts checked against what the AI actually claims.
  3. Root causeAI visibility was judged by anecdote — one prompt, one day — with no sample, no baseline and no attribution back to traffic.
  4. FixA closed loop — discover, measure, diagnose, prioritise, fix, validate, learn, attribute — with opportunities turned into briefs and experiments, GA4 AI referrals attributed, weekly runs on a durable scheduler and the client report archived.
  5. Measured Delivered13 MCP tools · 2 approved opportunities executed on the pilotwindow: staging, piloted on a dental clinic · Nothing is shown under n < 5 — by rule. No visibility uplift is claimed yet.
Open the proof →

Accounting firm, BucharestBuilt, awaiting client go

A professional-firm site with a quote builder and a verified assistant

  1. Issue detectedProspects wanted a price range now; juniors answered the same tax questions every day; the site was a brochure.
  2. VerificationThe prospect's path walked from first question to a price: no page answered it. The questions juniors repeat daily became the approved knowledge base the assistant is allowed to use.
  3. Root causeA brochure site: nothing on it could give a number or an answer, so every question landed on a person.
  4. Fix56 prerendered RO/EN pages, a QuoteBuilder (scope → indicative fee), an assistant that answers only from the approved knowledge base and never invents tax rules, a knowledge hub for SEO/GEO, a lead console with GDPR consent and a demo kit for sales presentations.
  5. Measured DeliveredLighthouse 100 × 4 · 15 end-to-end tests greenwindow: private staging URL, presentation-ready · Built, awaiting client go — quote and lead volumes are not measured until it is live.
Open the proof →

Consumer health product, liveLive

A lab-results explainer, GDPR art. 9 by design

  1. Issue detectedPeople google each value on their lab report, one by one, in fear — and health data is the most sensitive category there is.
  2. VerificationVerified end to end with real reports, including the trend across reports of the same person; every value cites its page and row on the source PDF.
  3. Root causeA search engine cannot read the interval printed on that specific report, and a model left alone will guess numbers. Trust needs the number to come from the paper, not from the model.
  4. FixA deterministic parser reads every value and interval from the PDF; the model only writes the words; explicit health-data consent before anything; one-click export and erasure; one cookie, no third parties. It never diagnoses.
  5. Measured DeliveredLive · zero analytics, zero third-party requestswindow: production · Usage is not measured — by design. No analytics on health data.
Open the proof →

Home-care e-commerce, ~1,500 orders/monthBuilt, awaiting client go

An edge storefront replacing WooCommerce

  1. Issue detectedWooCommerce at ~1,500 orders a month: plugin conflicts, a slow checkout, hosting bills — and e-invoicing that must not stop for a day.
  2. VerificationThe catalogue and the order flow rebuilt on staging and measured there: 579 URLs, accessibility 100, LCP under 2.5 s, 509 products in the edge database.
  3. Root causeA general-purpose plugin stack carrying an order volume it was never designed for — speed, stability and hosting cost all paid for it.
  4. FixA custom storefront with the catalogue in an edge database, a back-office designed for the order volume, historic order import planned for 50–100k orders, invoicing and payment providers kept, tracking and consent built in.
  5. Measured Delivered579 URLs · accessibility 100 · LCP under 2.5 swindow: staging · Production untouched until the client's go; no order or revenue effect is claimed.
Open the proof →

Internal operationsInternal

A control plane for a 51-project portfolio

  1. Issue detectedFifty-one projects, sixty-five workers, nine Cloudflare accounts — and no single place that knew what was deployed, broken, stale or ready to launch.
  2. VerificationDiscovery across GitHub and Cloudflare registered every project; daily audits from the edge — performance, accessibility, screenshots — replaced memory with measurements.
  3. Root causeKnowledge lived in people's heads and in nine separate dashboards, and "unknown" was silently read as "fine".
  4. FixHealth and readiness scores where UNKNOWN is never zero, launch gates with waivers, regression sweeps, 36 MCP tools, and recommendations whose impact is measured after they ship — read-only toward every child repository, by rule.
  5. Measured Attributed19 recommendations validated with before/after numberswindow: daily audits across 51 projects · Before/after measured per recommendation; other changes shipped in the same window were not isolated.
Open the proof →

Next step

No proof is yours until it is about your business.

See what Valhalla would find on your site →
Analyse my businessWhatsApp