How long did Semoria take to build?

Six weeks from a standing start to a multi-tenant production SaaS with three paid tiers, a 30-day free trial, three free tools, a programmatic blog, automated email flows, and full analytics. The work covered architecture, authentication, payments, voice fingerprinting, content generation, scheduling, the marketing engine, and security hardening. The full build inventory is 424 TypeScript files, 73 API routes, 64 database migrations, 47 blog posts at launch, 27 transactional email templates, and 5 n8n workflows.

What is multi-agent orchestration in AI development?

Multi-agent orchestration is the practice of running several AI coding agents in parallel against different parts of the same codebase, with a lead agent coordinating their work. Each agent gets an isolated workspace, a scoped task, and a clear definition of done. Instead of a single agent working through tasks sequentially, the lead splits independent slices (a new API route, a refactor, a test suite, a marketing page) across parallel agents that run at the same time. The lead reviews, integrates, and arbitrates conflicts. The result is real wall-clock compression on multi-feature work without sacrificing review quality.

How do you stop parallel AI agents from conflicting?

Two safeguards. First, every parallel agent works in an isolated git worktree so that file edits cannot collide at the filesystem layer. Second, the lead agent scopes tasks so the surface areas do not overlap, which is the same discipline a senior engineer applies when splitting work across a team. When agents do touch shared files (shared types, configuration), the lead serialises those changes and runs them through review before integration. The human role shifts from writing code to arbitrating scope, reviewing output, and making the judgement calls that AI is bad at.

What is Semoria's tech stack?

Next.js on Vercel for the app and hosting, Supabase Postgres for data with row-level security on every table, Supabase Auth for sign in, Stripe for subscription billing, Resend for transactional email, n8n for workflow automation, PostHog for analytics and product funnels, and Sentry for error monitoring. The AI layer uses Claude via OpenRouter for generation, Perplexity Sonar Pro for research grounding, and Anthropic Haiku for the free tools. The lean stack runs comfortably for around £40 a month at 50 paying users, with clear unit economics as the user base grows.

What does it prove Agenticise can build for clients?

That the agency can ship platforms, not only single-workflow automations. Semoria is a multi-tenant SaaS with payments, auth, security hardening, AI integrations, and a full marketing engine, all designed and built by Agenticise. The same methodology, voice modelling work, and content engine that runs in Semoria every day is what underpins the tone-of-voice work Agenticise delivers for clients. The Semoria build is the proof point for the under-8-weeks idea-to-production claim that anchors the agency offer.

Is Semoria a separate company or part of Agenticise?

Semoria is a product built and owned by Agenticise, positioned as 'by Agenticise' for credibility transfer. The agency continues to deliver bespoke automation work for clients in the £4M to £160M revenue band. Semoria runs as the productised tone-of-voice content engine for marketing functions that want the underlying methodology without commissioning a custom build. The two businesses share infrastructure, design language, and a single founder, which is why the build velocity is what it is.

Case Study: Semoria

From Idea to Production SaaS in 6 Weeks

Semoria is a multi-tenant LinkedIn content SaaS with voice fingerprinting, research-grounded drafting, scheduling, three live paid tiers, three free tools, and a full marketing engine. We designed and shipped it in six weeks, then handed the build methodology back to Agenticise as proof we can ship platforms, not only single-workflow automations.

Book a Discovery Call Visit semoria.io

The Build, in Numbers

Every figure below is from the production codebase at launch, not estimates.

6 weeks

Idea to production SaaS

424

TypeScript files

API routes

Database migrations

Blog posts at launch

Transactional email templates

The Story

Semoria started life as bespoke tone-of-voice agents for Agenticise clients. Marketing functions across multiple sectors had the same problem: a brand voice they had spent years sharpening, ideas in abundance, and no human capacity to publish consistently in that voice every week. We built custom engines that solved it for one team at a time, including the FPC content engine that took output from 1-2 posts a month to 2+ a week without a hire.

By early 2026 the pattern had repeated so many times across different marketing functions that the bespoke route was clearly not the right shape for most of them. The £8,000 to £20,000 build cost was a stop sign for the teams that needed the methodology most. The right shape was a subscription, on the same underlying engine, with the same human-in-the-loop control.

So in six weeks Agenticise designed, built, and shipped Semoria. A multi-tenant SaaS with payments, auth, AI integrations, security hardening, and a full marketing engine, on a stack that costs under £40 a month to run at 50 paying users. The full origin story is in the first post of the series.

Read Post 1: Why We Built Semoria

The Build

Six weeks was possible because of multi-agent orchestration in Claude Code, not because one AI worked harder. A lead agent split independent slices of the build across parallel sub-agents running in isolated git worktrees. One would draft a new API route, another would refactor the billing flow, a third would write tests for the voice engine, and a fourth would build a programmatic blog page. The lead reviewed, integrated, and arbitrated conflicts. The human role shifted from writing code to arbitrating scope, judging trade-offs, and owning anything irreversible.

The full methodology, including the lead-agent and sub-agent pattern, what we deferred, when to switch between deep-work and parallel-work modes, and what humans still own, is covered in Post 2.

Read Post 2: The 6-Week Methodology

The Stack

A lean, modern SaaS stack runs Semoria for around £40 a month at 50 paying users. Every layer is chosen as a utility, not an endorsement. The full architecture, multi-tenant patterns, security hardening, and cost table at 0, 50, 200, and 500 users is in Post 3.

Next.js on Vercel

App framework and hosting. Auto-deploys from main.

Supabase

Postgres with row-level security on every table, plus auth.

n8n

Workflow automation for content pipelines and scheduled jobs.

Stripe

Subscription billing across three live tiers, plus promo codes.

Resend

Transactional email for trial, billing, and digest flows.

PostHog and Sentry

Analytics, funnels, and error monitoring from day one.

Read Post 3: Inside the Architecture

The Marketing Engine

The marketing engine was production-ready on day one, not bolted on after launch. Programmatic blog with FAQ schema and AEO-ready structure, three free tools acting as distinct conversion funnels, persona pages for programmatic SEO, content-calendar driven social automation, and 27 transactional email templates wired into the trial, billing, and digest flows.

Marketing channel	What we built
Programmatic blog	47 posts at launch, MDX with FAQ frontmatter rendered as JSON-LD FAQPage schema.
Free tools	Voice Analyser, Post Generator, Voice Score Card. Each is a contained value unit with its own conversion funnel.
Persona landing pages	Programmatic SEO across niche segments with intent-aware copy.
Email automation	27 templates covering trial onboarding, billing events, weekly digest, and feature discovery.
Analytics and funnels	PostHog funnels wired from first pageview through trial conversion to billing event.

Read Post 4: Building the Marketing Engine

The Product in Use

Live screenshots from semoria.io. A human reviews every output before it publishes.

Voice fingerprinting

A measurable voice signature per profile, trained on real published writing.

Research-grounded drafting

Every post grounded in recent industry research, with citations the reviewer can verify.

Series and scheduling

Generate as one-offs or 2 to 5 post mini series, then schedule across the week.

Dashboard and review

Approve, request a plain-English rewrite, or reject. Nothing publishes without a human.

See It Live at semoria.io

Frequently Asked Questions

Ready to Build Yours?

Bring the platform you have been waiting to ship, or the tone-of-voice problem you have been trying to solve at scale. In a 30-minute discovery call we will sketch the build, the methodology, and the right shape for your team.

Book a Discovery Call See All Case Studies