Week 8: Every surface tells a story

These two weeks weren't about the engine. They were about everything around it. The product is real — scanning live sites, shipping fix-ready code, running inside IDEs. But when someone landed on corexi.ai, none of that was visible. The site was explaining what Corexi could do instead of showing what it does.

Building in public, for real

We launched /journey — a weekly build log with what actually happened, what broke, and what we learned. Not a blog with placeholder "exciting update!" posts. This is the raw timeline of building a product from zero.

There's a newsletter behind it. Subscribe, get it every Monday. The landing page now features the latest three posts in a dedicated section, because if you're going to build in public, the public should be able to find it.

Platform page: show, don't spec

The old /platform page was a grid of identical cards describing features. It read like a PRD, not a product tour.

We logged into our own dashboard, screenshotted real screens — UX Score, findings list, fix code output, Neurodiversity Lens — and rebuilt the page around them. Each feature gets its own section with a real screenshot in a browser frame. The MCP Server section shows the actual JSON config on one side and the 9-tool grid on the other.

If someone lands on this page and still doesn't understand what Corexi does, that's on us.

1,007 analyses in 7 weeks

As of today, over a thousand UX analyses have been run through Corexi — from the homepage scan, the dashboard, and the MCP server combined. Seven weeks from first deploy to four digits.

We're not sharing user numbers yet — we're still in open beta and focused on quality over quantity. But we're actively onboarding scale-up and enterprise teams, and the feedback loop is working. People are using it, coming back, and telling us what to fix. That's the only metric that matters right now.

The rest of the site caught up

Methodology and Engine pages got rewritten. They were technically accurate but dry — now they lead with "why this matters to you" instead of "here's how we built it." Navigation got dropdown menus that group pages by what you're looking for: Product or Developers. Small change, big clarity.

People are reaching out

We're not actively raising, but inbound interest landed from both Iberia and Turkey over the past weeks — investors who found the product and reached out. We're grateful for the conversations and we're taking every meeting. The pattern we keep hearing: enterprise and scale-up teams need a continuous UX layer, and nobody else is building it.

We're heads-down on the product. But it's good to know the signal is there.