Series: Building in Public Journal | Week 4 of 4

There is a difference between a tool and a product. A tool runs once. A product has to keep working when a user signs in, runs an audit, reads the result, asks what to fix, exports the work, comes back next week, and gives feedback when something feels off. Week 4 was the week LITV AI SEO Agent 2.0 crossed that line. That is the distinction that defined Week 4. And it is the most honest thing I can say about what this sprint taught me.

If you are joining this series for the first time: I have been building the LITV AI SEO Agent 2.0 live during a four-week sprint called the Women in AI Accelerator, run by Build Club and hosted by Annie Liao and Caroline Ciaramitaro. Week 1 was architecture and choosing not to build the easy version. Week 2 was auth, staging, and the first real code commit. Week 3 was the unglamorous compliance and layers of backend work that holds the entire structure together. Week 4 was where the loop had to stick and the product around the engine had to materialise.

From Engine to Product: The Shift that Defines What Shipped in Week 4

The audit engine was always the centrepiece of the build. It crawls publicly accessible URLs, analyses them across Technical SEO, SXO, GEO, and AEO signal layers, and returns a more structured intelligence report. It runs in a loop: it enters a website, processes the allowed pages, aggregates the scoring, delivers the output, and waits for the next request.

What Week 4 made clear is that the engine being operational is not the same as the product being usable. The harder work is everything around the output: access control, delivery, data handling, error states, mobile behaviour, admin workflows, and the feedback path that tells you what users actually experience when the engine does its job.

That surrounding layer is what Week 4 was for. Here are the five highlights that defined it.

5 Key Highlights from the Week 4 Build

1. The Audit Loop Held and What that Means

This is the technical win I am most proud of from the entire sprint. The audit loop has to function at three stages: initial entry into the target URL, mid-stage signal processing across the four audit frameworks, and final output generation into a structured report from the layers of audit and visibility. If it breaks at any one of those stages, the failure is clear as day. If it holds across all three, I have the evidence that the architecture is sound.

The loop broke three times during Week 3 before it held consistently. Two breaks were in the signal extraction layer, where edge cases in structured data markup were not being handled correctly. Each break was fixed directly in the engine’s core logic, then patched through to the surface. The loop now holds on standard sites and on slow-crawl days where the pipeline is under more stress and on downtime days.

An AI-powered engine that fails silently is not an engine. It is a liability that breaks the loop and can run simple autofixes.

2. The Dashboard became Usable, unlike a Scratch Surface

The dashboard had to stop being fragile. Week 4 addressed the layout across desktop, tablet, and mobile views — tightening panels, making wide issue tables scroll inside their own containers, and making the interface feel calmer and more consistent across different screen sizes.

Accessibility hardening was also part of this. This is not the glamorous part of an AI product build. But it is the part users feel immediately, and the part that determines whether someone who is not technical trusts the product enough to use it a second time.

3. The Fix Pack became a part of the Workflow, Not as a Download

The Fix Pack is the action layer of the audit. It takes the findings from the Technical SEO, SXO, GEO, and AEO report and turns them into a prioritised set of recommendations that a user can actually work through.

In version 1.0, Fix Pack output was just a static download. Week 4 moved it towards a proper execution workflow. Paid users can now work with PDF and CSV outputs through clearer delivery paths, and the product is materialising to support the rhythm I care about most: audit, identify the gaps, prioritise the fixes, validate the key blockers, and re-audit for better indexing to take place. That cycle is the actual value proposition of the product. A dashboard full of scores with no path forward is just anxiety in a UI.

4. Telegram Delivery Got a Proper Verification Flow

Telegram delivery has been on the roadmap since early in the build. The idea is straightforward: users who want their audit results and Fix Pack outputs delivered directly to Telegram can connect the LITV bot, @litv_agentic_bot, through a clean verification step rather than manually pasting chat IDs or guessing what to do inside the bot. Week 4 tightened the backend and frontend around that flow. This matters for non-technical users who would otherwise abandon the setup at the first point of ambiguity.

5. Beta Users will Soon Be Inside the Loop

Beta licence keys are prepared for Build Club testers to access the paid-tier dashboard experience during the upcoming testing window. A standalone beta feedback form was built intentionally separate from the main product navigation to capture product feedback.

Final Conclusion: Nothing is Final When You are Building Something Serious

The Women in AI Accelerator is a four-week sprint, and the LITV AI SEO Agent 2.0 is not a four-week product. The sprint gave me structure, community support, accountability, and the enforced function to ship what I had been planning since before I joined the accelerator. But nothing about this build is 100% finished because nothing about the problem it solves is finished.

Why is it Not Finished?

AI search is evolving. The platforms that mediate it are evolving. The signals that determine citation and visibility will shift, affecting some of them before the end of this year. A product built to audit those signals has to be built with the assumption that the audit criteria will change. That is not a caveat. It is the full product and design brief.

The comprehensive audit and visibility engine inside LITV AI SEO Agent 2.0 was always the centrepiece of the build. But an engine without a usable product around it is infrastructure, and not a service. Week 4 was where the two finally met and they clicked.

What’s Coming for Demo Day

TBC.

Thanks to Build Club, Annie Liao and Caroline Ciaramitaro for hosting and facilitating this 4-week immersive AI building programme.