Case Study · 003Live · Paying enterprise customers

From whiteboard to paying enterprise customers.

Client
DELOS Analytica · Zürich, CH
Sector
Public Affairs · ESG
Engagement
Embedded product team
Duration
Q3 2024 — present
Team
5 Streavers · 2 DELOS
Stack
Next.js · Neon · Trigger.dev · OpenAI
4 monthsWhiteboard to live production
221,878Swiss parliamentary affairs indexed
49Languages in the monitored articles index
~25Paying enterprise customers · demos ongoing
The DELOS monitoring dashboard: a weekly feed where each card surfaces the issues detected and the stakeholders involved, with a search bar and filters across the top.
What we shippedThe Monitoring workspace — every signal DELOS gathers, triaged into a weekly board with issues and stakeholders attached to each item.
The DELOS Reporting view: a generated board-ready report with an executive summary, strategic-horizon sections, and a 'Top Articles of the Week' rail.
Board-ready outputEvery week compiles into a cited, board-ready report — quadrant summaries up top, the week's key articles down the side.
01A new category of intelligence, born in Zürich.

The category exists. Nobody had built its operating system.

Founded
2024
HQ
Zürich, Switzerland
Market
Enterprise public affairs & ESG teams in EU/UK
Backers
Bootstrapped
Competes with
Lari Digital, Demosquare, among others

DELOS sells into one of the most underserved enterprise functions: public affairs and communications teams accountable for tracking thousands of stakeholders, regulators, journalists, NGOs and policy threads — and translating that noise into board-ready intelligence on a weekly basis.

The incumbents in this space are media-monitoring databases with dashboards bolted on. DELOS' thesis: collaboration, media monitoring and political intelligence belong in one platform — the Public Affairs Operating System — with AI doing the reading and humans elevated to judgment and validation. Everything revolves around one central entity, the Issue: a public affairs matter, news item or risk event that needs the organization's attention, linked to the Stakeholders — political actors, regulators, media figures — who move it.

When Silvan Krähenbühl, DELOS' founder and CEO, came to Streaver, the product existed as a vision document, a set of Figma sketches, and three signed letters of intent from Tier-1 European corporates. There was no codebase. There was no engineering team. There was a runway clock.

02The Challenge

Four hard problems, all to be solved at once.

DELOS' signed letters of intent had already been written into commercial procurement cycles. Slipping the launch wasn't a missed milestone — it was a missed market window. The MVP had to be live, in front of paying customers, in sixteen weeks. Inside that window were four problems that don't typically coexist in a single product.

01

AI matching that earns trust

Every newly ingested article and parliamentary record is scored against the organization's Issues and Stakeholders — continuously, and with every suggestion inspectable. Editors accept or decline each AI-generated reference in a structured triage workflow. A black box that hallucinates a regulator's position is worse than no AI at all in this market.

AI Architecture
02

Many providers, one model

News flows in from two commercial providers — LexisNexis and Opoint — at enterprise volume, plus the Swiss Parliament's open data. Ingestion had to normalize every provider into one model, including a provider-neutral source-authority rank, and stay resilient to schema drift — without a six-month data engineering build-out.

Data Infrastructure
03

An interface that disarms novices

The buyer is a head of public affairs, not a power user. The first ten minutes had to feel less like a database and more like a researcher who already knows their portfolio. Every screen had to surface the next sensible action.

Product Design
04

Swiss-grade governance from day one

Multi-tenant organizations with four roles, restricted issues with enforced row-level filtering, SSO, audit-oriented activity tracking, GDPR posture. Standard for European enterprise sales — frequently fatal to startups that try to retrofit it later.

Enterprise Readiness
We interviewed three other studios. Streaver was the only team that pushed back on our architecture before the contract was signed — and the only one whose engineers had already shipped agentic systems into production.
Silvan KrähenbühlFounder & CEO · DELOS
03Selection

Why DELOS chose Streaver.

Silvan ran a structured vendor selection across three agencies. Streaver won on four criteria.

Production AI experience, not prompt-jockeying.

Streaver had already shipped AI systems that real customers depend on — not demos. The reference checks happened on Slack with prior CTOs, not on a curated case study page.

Time-zone and culture alignment.

Montevideo and Zürich share most of a working day. Daily standups happen at 10:00 CET with no ceremony. Two of our engineers had previously worked with Swiss clients and understood the directness of the feedback culture.

A predictable delivery model.

No shadow offshoring. Every engineer on the engagement works client-facing and ships from day 1 — a stable, committed team, unchanged since the initial concept.

Ownership, not staffing.

Outcome ownership instead of hour-based staffing. Streaver committed to delivering sustainable outcomes — anchored by a fractional CTO engagement and a stable team — rather than just billing hours.

04Architecture

One pipeline, two domains: media and politics.

The platform's spine is an ingestion pipeline. News from LexisNexis and Opoint flows through AWS (Lambda, SQS, S3) into one normalized model, indexed into OpenSearch across 49 languages. Every source carries a provider-neutral editorial rank — a 1–5 source-authority scale, supplied natively by one provider and mapped from the other's own ranking — so users filter by source quality without ever caring which provider an article came from.

On top of the pipeline sits the triage loop. Scheduled monitoring scores every newly ingested article and parliamentary record against each organization's Issues and Stakeholders; candidates above a per-domain threshold land as pending references in the AI Inbox, and below-threshold noise never reaches a human. Editors accept or decline each reference — an accepted reference is Selection membership, immediately scoping the watchlist and feeding the weekly reports, daily digests and board-ready briefings. One workflow, two domains: media and Swiss politics.

The political side is not hand-modelled. Stage chains for each affair type are derived from the Swiss Parliament's open-data corpus — 221,878 affairs, 57,574 labelled events — by measuring the event walks affairs actually take, stored versioned and re-derived monthly with a drift report. The first design used four hand-authored process templates; measuring the corpus replaced them.

The upstream API overwrites records in place, so “what changed” cannot be read from the current document. The platform snapshots each tracked affair and diffs on stable ids and content hashes, ranking every change by severity to order the watchlist email — and reports are denormalized at generation, so a past report never mutates. The newest capability, now rolling out, forecasts legislative timelines and outcomes from measured stage-transition durations and probabilities — including the measured discovery that median durations don't add up, so cumulative estimates are computed separately rather than summed.

DELOS system architecture diagramDELOS system architecture: LexisNexis, Opoint and the Swiss Parliament's open data feed an AWS ingestion pipeline that normalizes every provider into one model with a 1–5 editorial rank. Trigger.dev background tasks generate AI references, reports, change detection and legislative forecasts. Editors triage AI-suggested references in the AI Inbox, accepting or declining them. Data lives in Neon Postgres and OpenSearch behind a Next.js application on Vercel, with reports delivered to the public affairs team by email and SMS.SOURCESINGESTIONBACKGROUND JOBSTRIAGESTORAGEAPPLICATIONDELIVERYLexisNexiscommercial news · SLAOpointweb news · multilingualSwiss ParliamentOpenParl · affairs · votesAWS · CDKIngestion pipelineLambda · SQS · S3Provider normalizationSchema-drift resilientEditorial rank 1–5TRIGGER.DEV · 01AI referencesitems → issues · stakeholdersTRIGGER.DEV · 02Reportsweekly · daily · watchlistTRIGGER.DEV · 03Change detectiontracked affairs · state machineTRIGGER.DEV · 04Forecastingtimelines · outcomes · stage statsAI INBOXHuman triageAI-suggested referencesSearch · ad-hoc discoverySelection · tracked itemsDECLINE→ kept out of reportsACCEPT→ selection & reportsNEON POSTGRES + OPENSEARCHPrisma model + search indexIssues · stakeholders · references · articles · auditVERCEL · NEXT.JSAI Inbox · Search · SelectionTypeScript · RSC · SSO · roles · audit trailREPORTS OUTPublic affairs teamResend email · Twilio SMSAccepted signal compiles into reports · delivered on per-organization schedules and timezones
Figure 1 · DELOS system architecture · simplified for clarity
The DELOS Issues board: an impact-versus-urgency quadrant plotting detected issues as colour-coded cards, with a 'Generate Issues' action.
Product · IssuesIssues plotted on an impact/urgency board — each organization sets its own impact and timeline midpoints, and priority derives from importance × urgency, demoted only when the org can't influence the outcome.
The DELOS Stakeholders map: a grid of Tier 1 to Tier 3 rows across Media, Government, Politics and Research columns, with a 'Generate Stakeholders' action.
Product · StakeholdersStakeholders mapped into tiers across Media, Government, Politics and Research — the core public-affairs intelligence view.
05Decisions

Six technical bets that defined the product.

01

Per-task model routing through one registry.

Every AI task resolves its model through a central registry with three tiers — cheap, medium, heavy. High-volume, narrow tasks run on the cheap tier; anything producing prose a customer will read resolves heavier. Resolution runs global default → environment → per-organization override, so a tenant can be moved to a different tier without a deploy, and AI summaries are persisted rather than regenerated. Spend maps to task difficulty instead of defaulting to the frontier model.

02

A quality gate, then a human in the loop.

AI never publishes directly. Every AI-generated reference passes a per-domain score threshold — low-scoring suggestions are dropped before an editor ever sees them — and everything above it lands as pending in the AI Inbox, where an editor explicitly accepts or declines it. Only accepted references reach selections and reports.

PrincipleIn regulated B2B, a system where a human explicitly approved every claim in the report is trusted faster than one that publishes on its own.
03

Buy the backbone. Build the edges.

We argued against building proprietary news crawling. Two commercial providers — LexisNexis and Opoint — give multilingual, enterprise-grade coverage with contractual SLAs. What we built is the layer that makes them one product: an AWS ingestion pipeline (Lambda, SQS, S3) that normalizes both providers into a single model, indexes everything into OpenSearch, and adds a provider-neutral editorial rank — a 1–5 source-authority scale — so users filter by source quality without caring where an article came from. The edge we did build ourselves: the Swiss Parliament's open data (OpenParl), modelled as a state machine of the legislative process, with change detection and outcome forecasting on top. Commercial backbone, custom edge — the right shape for almost every 'AI on top of external data' product.

DifferentiatorPolitical monitoring — integrated parliamentary processes and stakeholder tracking — is the platform's key differentiator, and it runs through the same AI Inbox, Search and Selection workflow as media.
04

Every pull request gets a full, disposable environment.

Opening a PR automatically creates an isolated Neon database branch, a Vercel preview deployment, a Trigger.dev preview environment, and its own AWS stack; closing the PR tears it all down. Reviewers click a link and test the real thing — background jobs included — before anything merges. From there, main deploys to staging and a promotion to the production branch ships to customers.

05

Decisions are written down.

Twenty-three architecture decision records — plus architecture docs and runbooks — document why the system is the way it is, from the original stack choice (July 2024) through background-job architecture, news-provider integration, report change-detection, and the forecasting design. New engineers, and increasingly AI agents, read the reasoning instead of reverse-engineering it.

06

The codebase is AI-agent-ready.

The repository carries canonical agent instructions, a faceted product glossary where every term lists the synonyms agents must avoid, scoped rules per area, and hard guardrails: versioned pre-commit and pre-push quality gates plus a hook that denies agents the --no-verify escape hatch (humans can bypass it; agents cannot), an environment-file access guard, and a human-approval step for every dependency install. In the repo's own words: 'AI has no accountability; humans do.'

06Honest

What didn't work. And what we'd do differently.

Retired · Sep 2025

The crawler we built, then turned off.

In early 2025 we built our own crawler — a Firecrawl-based proof of concept that went through four versions chasing long-tail sources. It never earned its keep next to the commercial providers, and crawl-source functionality was switched off in September 2025. Buying the backbone won, again.

Rebuilt · 2025

Three versions of the monitoring pipeline.

The monitoring pipeline is on its third major version. The orchestrated multi-step pipeline we shipped in April 2025 was rebuilt into today's realtime-monitoring v3 — each rewrite was cheaper than continuing to maintain the wrong shape, but we'd be lying if we called the first two versions anything other than expensive drafts.

Never shipped

The ADR that stayed on paper.

Not every written decision shipped. One architecture decision record chose a third-party extraction vendor that was never implemented — the record stays in the repo, marked as such, because knowing why we didn't do something is as useful as knowing why we did.

Late · Aug 2026

Evals arrived later than they should have.

The evaluation harness for the AI pipelines landed in August 2026 — two years in. We'd have wanted it from day one. Until it existed, quality lived in score thresholds and human triage, and we're honest that those are guardrails, not measurement.

07Outcomes

The numbers that mattered to DELOS.

We focus on outcomes the business uses internally — not vanity metrics. Each result below is grounded in the engagement's own record: the codebase, its decision records, and its delivery history.

no codebase16 weeks to live

Whiteboard to live production

From signed engagement to a running production environment — the first merge into the production branch lineage landed in October 2024, inside the fixed-fee phase.

media onlymedia + politics

Two domains, one workflow

Swiss parliamentary monitoring ships through the same AI Inbox, Search and Selection surfaces as media — political intelligence without a second product to learn.

analyst-compiledauto-generated

Reports on autopilot

The Weekly Media Report is fully auto-generated and Issue-centric; daily keyword digests are AI-composed but editable before they go out.

one model for alltiered routing

Model cost under control

Every AI task resolves its model through a central registry — cheap, medium or heavy — with per-organization overrides, so spend maps to task difficulty.

3 LOIs~25 enterprise customers

Commercial traction

From three signed letters of intent to roughly 25 paying enterprise customers, with several demos in flight — bootstrapped, no outside capital.

no telemetrySentry tracing

Monitoring & observability

Every exception surfaces in Sentry — errors, performance, and session replay — so regressions are caught and triaged in hours, not when a customer reports them.

Streaver doesn't feel like a vendor. They feel like the engineering team I would have built if I'd had eighteen months and a Swiss salary budget.
Silvan KrähenbühlFounder & CEO · DELOS · Zürich
08The Team

Five Streavers. Two from DELOS. One product.

Every person named below was on the team at week one and is still on the team today. No staffing churn, no shadow offshoring. This is the team that shipped, and the team that will still be shipping in 2027.

Fede
Fede
Fractional CTO

Built the system from scratch, co-creating the MVP from rough ideas in 3 months. Then became their official CTO, leading the tech team to ship a well-rounded product. Still going.

Feld
Feld
Team Leader

Leading the Delos team, I turn client vision into shippable work, keep delivery steady, mentor devs, and raise our quality/efficiency bar. As Cursor Ambassador, I lead AI adoption.

NicoW
NicoW
Senior Full-Stack

Built the system from scratch, keeping direct client communication and solving key tech challenges. Led political monitoring integration gathering and analyzing public affairs data

Joaquín
Joaquín
Junior Full-Stack

I run Delos releases and demos, set up our worktrees, and keep us current on AI: Claude Code, skills, workflows, and complex features like LLM-judge scoring.

Cate
Cate
Senior Product Design

Leads product design across the platform, turning complex requirements into intuitive, accessible experiences that simplify workflows. Sets core product patterns and shapes growth.

How the engagement is structured

Cadence

Two-week sprints. Daily standup at 10:00 CET. Sprint review with Silvan and DELOS product on Fridays. Monthly retro and quarterly business review.

Communication

Shared Slack workspace, Linear for engineering, Notion for product documentation. DELOS has full read access to every channel and repository.

Pricing

Fixed-fee per milestone for the first sixteen weeks. Monthly retainer with capacity commitment thereafter.

IP and security

All IP transfers to DELOS on payment. Audit log and access reviews monthly. Two of our engineers hold the credentials they need; no shared accounts.

Timeline

WEEK 00Engagement signedThree LOIs in hand · zero code · architecture sketched on a Friday whiteboard.
WEEK 02Architecture frozenNeon + Vercel + Trigger.dev confirmed · first architecture decision records written (July 2024).
WEEK 03First AI proof of conceptA single-chain agent app ships as the first AI proof of concept in early August 2024 — later folded into the product.
WEEK 14Production environment liveFirst merge into the production branch lineage lands in October 2024 — a production environment exists before the fixed-fee phase closes.
WEEK 16Production launchLive with the foundation in place: stack, background jobs, first monitoring pipeline. Fixed-fee phase ends; the engagement moves to a monthly retainer.
2025Monitoring matures, politics beginsSMS notifications ship in May, the monitoring pipeline reaches its third major version in June, Swiss Parliament data enters the pipeline in September, and the Weekly Media Report lands in November.
EARLY 2026Ingestion at enterprise scaleLexisNexis ingestion lands on the AWS pipeline in January; authentication migrates to Better Auth in April.
MID 2026The differentiator shipsAI Inbox triage in June; Opoint as a second provider, watchlist change detection and the central model registry in July; the eval harness and empirical legislative forecasting in August — the newest pieces now rolling out.
09Stack

Boring choices everywhere except where we couldn't afford them.

We don't reach for novelty. Every choice below earned its place — and could be operated by a small team without a dedicated platform engineer.

Languages & Runtime

  • TypeScriptstrict mode, end-to-end
  • Turborepoone monorepo, pnpm workspaces
  • Node.json Vercel + Trigger.dev

Application

  • Next.jsApp Router, RSC-first
  • Tailwind · shadcn/uidesign system, components
  • Better Authmagic link · SSO
  • Resend · Twilioemail + SMS delivery

Data & Infra

  • Neon Postgresvia Prisma
  • OpenSearcharticle search & retrieval
  • Trigger.dev24+ tasks: crons, AI, reports
  • AWS CDKLambda · SQS · S3 ingestion
  • Vercel · GitHub Actionshosting · 17 CI workflows

AI & Quality

  • OpenAI modelsvia the Vercel AI SDK
  • AWS Bedrock KBmanaged semantic retrieval
  • Sentryerrors · performance · replay
  • Jest · Playwright778 test files · 19 e2e specs
  • Neon branchingper-PR preview databases
Working on something similar?

Strengthen your tech with engineers who've shipped production AI.

Streaver embeds senior product teams inside companies building agentic and AI-native products. From whiteboard to live customers, with the same engineers throughout.