I founded Vritto, a private personal organizer that connects your plans, people, records, and routines across web, iPhone, iPad, and Android. It brings together the parts of life that usually sit in separate apps, with focused tools for each area and connections that make information useful beyond the place it was entered.
As founder and CEO, I lead product, design, engineering, and AI. My work spans how each part of life is organized, how information connects, what assistants are allowed to see and change, and how the business makes money.
The Product Bet
Most personal software understands only one slice of a person. A calendar knows time. A finance app knows transactions. A contact app knows names. A health app knows measurements. The user still has to connect those facts and coordinate what happens next.
Flexible workspaces solve a different problem, but they often begin with a blank canvas. Users have to design databases, properties, views, and conventions before the system becomes useful. That flexibility creates its own maintenance burden and still leaves every category represented as a generic page.
Vritto takes a more opinionated approach: structure each area according to what it represents, then connect those areas through one private record. A subscription behaves like a subscription. A trip has legs, stays, places, and plans. A person can be connected to dinners, gifts, memories, and future commitments without being duplicated across them.

Connected by Design
Each area in Vritto has the fields, views, and actions its subject needs. Orders track deliveries and returns. Trips bring flights, stays, and plans together. People connect to birthdays, gifts, and shared experiences. The same person, place, or record can appear wherever it is relevant without being entered again.
That distinction shapes the product in three ways:
- Focused on its own. Orders can model shipments, pickup windows, returns, refunds, merchants, and spending without forcing that structure onto unrelated records.
- More useful together. A dinner can connect a person, reservation, place, task, and planned spend. A trip can collect flights, stays, packing, dining, and memories around one experience.
- Readable without AI. Modules, dashboards, reports, and relationships remain useful on their own. Intelligence is a capability layered on top, not a dependency for understanding the user's data.
Intelligence with Boundaries
SahAI is Vritto's built-in assistant. It can answer questions across permitted records, prepare a brief for the day, and help add or update information. Users control its access and whether changes require review.
External assistants can connect through the Model Context Protocol. Vritto's MCP server works with ChatGPT, Claude, Gemini, and Grok, and is approved for Anthropic's Claude directory. Users choose which supported modules each assistant can access and whether it can make changes. Sensitive areas remain unavailable unless enabled, and access can be revoked from Vritto.
AI decisions are made on evidence rather than instinct. Model and tool-routing choices for SahAI are scored on a 276-case labelled evaluation set that measures accuracy, latency, and cost per turn across Gemini, Claude, and OpenAI models. Automatic capture of receipts, orders, bills, and bookings from Gmail passed Google's restricted-scope verification and an independent CASA security assessment before it reached anyone's inbox.
This creates a deliberate separation between the record and the intelligence. The data lives in Vritto. The user can choose whether intelligence comes from SahAI, an external assistant, or nowhere at all.

Across Web, iPhone, and Android
Vritto uses a shared backend across its web, iPhone, and Android apps. Records and permissions follow the same rules on every platform, while navigation and interactions are designed for each device.
The native apps are built in SwiftUI and Jetpack Compose, with wide layouts for iPad. They include module workflows, account and subscription flows, notifications, and device integrations. Before release, each app was audited screen by screen against the web, and 737 findings were closed; each release is still checked through real workflows on devices alongside automated coverage checks.
Building across three platforms makes consistency a product responsibility. A feature needs to carry the same meaning, permissions, and useful information from one device to another, even when the interaction differs.
The Business
Vritto is subscription software with no advertising and no data sales, so the business only works if the product is worth paying for. There are three plans, from Essentials with no AI to Intelligence with SahAI, each priced in local currency across Stripe on the web, the App Store, and Google Play. A unit-cost model covering AI, cloud, and store fees sets each plan's AI allowance, and the company is built to break even at around a hundred subscribers.
From Project to Company
Vritto began in March 2026 as software I wanted for myself: one trustworthy place for a life spread across too many applications. Building the first modules exposed a larger product opportunity. The difficult part was not adding more categories; it was defining a system that could hold very different kinds of information without flattening them into generic records or turning the interface into a maze.
That work evolved into Vritto, Inc., founded in 2026. The company is being built around a straightforward promise: make useful subscription software, keep incentives aligned with the people using it, and treat privacy and user control as product architecture rather than policy-page language.
This page documents the product decisions and work behind the company. The Vritto website explains the product, plans, and availability.
Where It Stands
Live: web, iPhone, iPad, and Android apps in seven countries; 35+ connected modules; dashboards and notifications; SahAI; an MCP server for external assistants; automatic capture from email; and local-currency plans on three billing systems.
Now: growing in the launch markets and deepening the workflows people rely on most, especially automatic capture, which turns the email a person already receives into an organized record without manual entry.
My Role
As founder, I decide what to build, in what order, and how it should work. I design the experience and build across the apps and backend services, including the AI layer and the controls around it.
Three decisions shape that work: give each area of life the structure it needs, connect records without making users maintain those connections by hand, and keep the product useful when AI is turned off. Those choices guide the data model, interface, subscription offering, and release priorities.
My focus now is growth in the launch markets and deepening the everyday workflows people come back to.
