AI productivity·Illinois, USA
Otteri AI
All-in-one AI productivity workspace
Otteri set out to replace a stack of single-purpose AI subscriptions with one workspace. Fluid Web led the greenfield build and took it from an empty repository to a launched product with paid tiers and a browser extension in roughly six months.
What we walked into
Operators were paying for several AI tools at once — one for writing, another for research, another for images — with no shared credits, no shared context and a separate subscription for each.
Otteri was the answer to that: one workspace, one subscription, multiple models. Our founder led the build with the same team behind Treply, both products belonging to the same owner.
The problem
Aggregation products live or die on breadth arriving fast enough to be credible. A workspace that only does two of the five things a user came for is worse than the fragmented stack it replaces, because now they are paying for it as well.
That meant shipping a wide surface area quickly, without the product becoming a loose collection of wrappers around other people's APIs.
One workspace across multiple model providers
Chat across multiple models, research, content generation, image and media creation, and document intelligence over PDFs, web pages and video — all under one login, one credit pool and one subscription.
The provider layer had to be abstracted from the start, because a product whose entire premise is multi-model cannot have vendor specifics leaking into feature code.
- Multi-model chat under a single account and credit pool
- Research and long-form content generation flows
- Image and creative media generation
- Document intelligence across PDFs, websites and video
- Prompt library and browser extension for in-workflow use
Breadth without becoming a pile of wrappers
The failure mode for this category is a product where each capability is a thin, disconnected shell around a different API. Users feel it immediately — nothing shares context, and the whole is worth less than the parts.
Shared account, credit and context models underneath every surface are what made it one product rather than several bolted together.
Launched with real subscriptions, not a waitlist
Otteri launched with paid Pro and Teams tiers and a Chrome extension, roughly six months from an empty repository. Multi-seat team plans were part of the architecture rather than a later addition, since the team plan is where this category's revenue concentrates.
The hard parts
Shipping wide and fast simultaneously
Aggregation products need breadth to be credible at launch, which pulls directly against the usual advice to ship narrow. Getting there in six months meant shared foundations doing a lot of work across surfaces.
Provider abstraction as a founding constraint
With several providers behind one interface from day one, the abstraction had to be right early. Retrofitting it across an existing multi-model product would have been a rewrite.
Credits across unlike operations
A chat message, a research run and an image generation cost wildly different amounts. Presenting that as one comprehensible credit pool is a product design problem as much as an engineering one.
How it ran
Greenfield start
Empty repository, shared team with Treply, our founder leading the build.
Core surfaces
Multi-model chat, research, content and media generation on shared account and credit foundations.
Document intelligence and extension
PDF, web and video understanding, plus a Chrome extension for use inside existing workflows.
Launch
Shipped with paid Pro and Teams tiers roughly six months from the start.
Results
Otteri went from an empty repository to a launched product with paid Pro and Teams tiers and a Chrome extension in approximately six months, under Fluid Web leadership.
The workspace covered multi-model chat, research, content and media generation, and document intelligence across PDFs, websites and video — a breadth most aggregation products take considerably longer to reach.
Our involvement ended when our founder moved on. The product continued for a few months afterwards and is no longer actively operating, so we make no claims about its commercial performance.
Built with
Scope of our work
Fluid Web led the engineering build through to launch. Our involvement ended with our founder's departure, and we have no visibility into usage or revenue figures — we present this as a build-and-launch engagement, not an ongoing product success story.
Got something similar?
Tell us where delivery is stuck. We will give you an honest read on scope and shape before anyone talks contracts.
Book a technical review
