The platform
One relationship graph, with the work layered on top
Storm OS maps what your company actually has, a web of people and companies, and lets each relationship play every role it really plays for you. On top of that sits the work: the pipeline, the billing structure on a deal, the proposal your client signs, the invoice they pay, and the project you deliver. Five agents read all of it, none of them can change a record on its own, and everything on this page is in the product today.
What's inside
Storm OS is the platform, and these are the products that run on it.
Storm Eye is what the price buys, and the three beside it are separate offerings, free for early access members for at least a year. Storm Finance and Storm Marketing still carry a beta label.
Storm Eye
On every planEvery relationship you have
Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them.
See Storm Eye
Storm Project
IncludedThe work after the win
Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current.
See Storm Project
Storm FinanceBeta
IncludedGet paid for it
Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid.
See Storm Finance
Storm MarketingBeta
IncludedReach them again
Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on.
See Storm Marketing
Storm Service
NovemberAfter the invoice clears
The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers.
What it will do
The relationship graph
One record per person, one per company
Every person and company is one record carrying up to three roles, customer, investor, and partner, each with its own type, engagement level, and scores. Add a role with one tap and the record shows up in that pipeline, without a copy ever being made.
- Seven engagement levels, from Not Yet Engaged to Re-Engaging, the same across all three pipelines.
- Fit and activity scores built from scoring rules you control, with a panel that shows exactly why a score landed where it did.
- Duplicate detection when you add or import records, with a side-by-side merge that keeps every link intact and can be undone for seven days.
Pipelines
Three pipelines on day one, each built for a different game
Selling, raising, and partnering do not work the same way, so their pipelines should not pretend to. All three arrive with researched stages and thresholds, and every one of them is yours to change without writing code.
Sales
Deals carry amounts and stage probabilities, so the pipeline states a weighted forecast you can actually plan against. Line items, ramped pricing, and billing schedules live on the deal, ready for the contract.
Investor
The raise, modeled on how a raise actually moves: warm intros, first meetings, diligence, committed, wired. Check sizes roll up against your target so you always know how much is real and how much is conversation.
Partner
Partnerships carry no amounts, by design, because treating a reseller conversation like a deal ruins both. Progress is an agreement checklist moving toward live, and anything sitting too long gets flagged.
Staleness thresholds flag anything sitting too long in a stage and feed the Needs Attention list on your home screen, and you can add as many pipelines as you need, per product line, region, or experiment.
The money on a deal
A billing structure that matches how the contract is actually written
Most CRMs give a deal one amount box and hope you round in their favor. A deal in Storm OS carries line items instead, and every line says how much, how often, and when the money arrives. Twenty-five seats billed monthly, an implementation fee split across signature, acceptance and completion, and a migration quoted under list, all on the same deal, all adding up on their own.
Every charge on its own line
Quantity and unit amount on every line, a billing frequency of one time, monthly, quarterly or annually, and a discount measured against the catalog list price so a line says out loud what it gave away. Sell them ten more seats and you change one number in one place.
A payment schedule you shape
Pick a shape, everything up front, fifty fifty, fifty twenty-five twenty-five, or thirds, and the milestones are laid down with dates and amounts. Then edit any of them, because sometimes the deposit is really due on the first Monday of the quarter, and only a real date can say that.
- Frequency lives on each line, because a real contract usually has a one-time fee and a subscription sitting next to each other.
- A milestone carries its own words, and those words are what the client reads later on the invoice.
- Split a total three ways and the parts still add back to the exact amount, down to the last cent.
- Set a discount ceiling per catalog item, and a price below it is flagged before the proposal goes out, while there is still time to fix it.
- Investor and partner deals carry no amounts at all, by design, so none of this is forced onto a pipeline that does not want it.
- You never type a total, because the one-time amount, each recurring frequency, total contract value, and cost and margin if you are allowed to see them are all calculated from the lines every time you look.
From there it leaves the deal screen, the proposal’s pricing table and payment schedule are built from these same lines, and every invoice is raised from a milestone in the same schedule. The number your client is quoted, the number they sign, and the number they are billed are one number, calculated once.
Proposals
Write it, send it, get it signed, all on the deal it came from
Almost no CRM will let you write the document. You export a quote, rebuild it in a design tool, upload it to a signing service, and then hold three versions of the same price in your head and hope they match. Storm OS builds the proposal on the deal, so there is only ever one price and it belongs to the deal.
What your client opens
A document with your logo, your colors and your fonts on it, so the first thing your client sees is your brand. The pricing table and the schedule are the deal’s own line items, so a price you changed at four o’clock is right in the document at five.
What you see back
Every event the link recorded, against a name and a time. When you can see that finance opened it twice and nobody reached the terms, you know what the next call is about.
- A block builder on the deal: cover, headings, text, images, two-column layouts, terms, the pricing table, the payment schedule, and one signature block.
- Your branding is locked onto the proposal when it goes out, so a rebrand next year cannot quietly rewrite a document somebody already signed.
- PDF, Word and the web page are all generated from the same document, so the three can never disagree, and the Word file is there for the client whose lawyer redlines in Word.
- E-signature with a one-time code emailed to the signer, a typed name, versioned consent wording, and the time recorded.
- The moment it is signed, a sealed copy of exactly what was signed is stored: blocks, prices and terms, so "that is not the version I agreed to" has an answer.
- You countersign from your side and the deal moves.
- Investor and partner proposals refuse the pricing blocks outright, because those pipelines carry no amounts.
- Already have a contract you like? The Proposal Agent reads it and hands back a proposal draft you edit, with the live pricing block added straight from the deal, so no number is ever retyped by hand or by the AI.
Storm Finance Beta
The invoice comes from the schedule they already agreed to
You do not raise an invoice in Storm OS by typing an amount into a blank form. You raise it from a milestone on the deal, and the line, the amount and the wording your client already read are all sitting there. Then it goes out with its own payment page.
- Card payments run through your workspace’s own Stripe account. The money moves from your client to you, and it never touches ours.
- Not everybody pays by card, so bank transfer details, Zelle, Venmo, PayPal and a plain payment link are all fully supported, and you choose which ones the page shows.
- A card payment marks the invoice paid on its own. Anything paid another way you mark yourself, and the method is recorded against it.
- Tax is a rate over the taxable items, rounded once over the base rather than once per line, which is the drift that leaves a total a cent out.
- Every invoice, every payment, and every proposal event sits on the same deal and the same customer record, so a year later the whole story is in one place.
Storm Project
Project management, on the record the work came from
Boards with columns you name and color, tasks with owners, start and due dates, priorities, statuses and dependencies, and a calendar across all of it. The feature list is what you would expect, the difference is where a project lives: it hangs off the opportunity, the company, or the person it came from, so the rollout you promised sits on the record of the customer you promised it to, and nobody has to keep two tools agreeing about the same account.
The board
Where a project opens. Columns you name and color, cards you drag between them, and the things that decide your day on the face of the card: who owns it, when it is due, how urgent it is, and what it is waiting on.
The task
Every task is a record of its own, with a status, an owner, a start and a due date, a priority, a description, and the task it is waiting for. Dependencies are advisory on purpose, so you get a heads-up while staying free to work in whatever order the day demands.
The calendar
The same tasks laid out by date, Monday first, with anything late in red. Drag one to a new day on a laptop or tap it on a phone, and the board and the list already agree.
Every project at once
The wall of what you owe and to whom. Each project is either attached to a record or marked internal, and progress is counted from the tasks rather than typed in, so nothing here can flatter anybody.
The project brief
A project that reads its own documents and keeps the brief current
Give a project the statement of work, the kickoff transcript and the change request, and it folds each one into a standing brief: what is settled, what nobody has answered, who owes what and by when, who the stakeholders are, and the client's own words for things.
- Each new document is read against the brief rather than against the whole pile, so the fortieth transcript costs what the first one did and reads better, because the brief has more in it by then.
- The brief knows what was agreed, so it can tell you when something new is not in it: a task nobody has written down, a scope change buried in a call, a risk worth naming out loud.
- Every one of those arrives as a proposal you accept or ignore. Nothing is written into the project until you say so.
- The brief stays a readable length on purpose, dropping what stopped mattering instead of growing forever.
- Close an opportunity and Storm OS offers to start the project there, carrying the customer and the stakeholders across.
- Anyone who can see a record can start a project from it, because the person who delivers the work is often not the person who sold it, and delivery does not need edit rights on your pipeline.
- Board, list and calendar are chosen per project, so each project can work the way the person running it prefers.
- A project can belong to a customer, an investor or a partner record, or to nobody at all when the work is your own.
- Project tasks join your relationship tasks in Tasks, the morning digest, and the notifications you already get, instead of forming a second inbox.
- The Context Agent reads a project like it reads a deal: what is done, what is late, who is waiting, and on which record.
The command center
Home answers one question: what needs my attention right now?
A founder with ninety seconds between meetings needs the whole picture fast. Home is a configurable widget grid, all pipelines at a glance, today's tasks, stale deals, and upcoming closes, and it loads instantly even when you are offline.
- Widgets keyed to how you work: all-pipeline overview, needs attention, my tasks, recent records, KPI tiles.
- Tasks with natural due dates, reminders, and one-tap completion from anywhere.
- A unified timeline on every record: notes, calls, meetings, stage moves, and changes, in one stream.
Reports and dashboards
Answers without a data hire
Every pipeline gets its own dashboard automatically, with a stage funnel, movements, forecast, and stale deals, and a report builder lets you ask questions across all your records, saved and shared with your team.
- What's new, what's moved, and what's closed, the questions you ask every week, are answered without any setup.
- Group by any field including the custom ones you add, with tables, bars, lines, funnels, and single-number tiles.
- Every table exports to CSV whenever you want it.
Private Rooms Beta
A page with your name on it, for the people outside your company
Investors, customers and partners need documents from you, and none of them should need a seat in your workspace to read one. A Private Room is a branded page holding exactly what one person or one company should see. They sign in with their own email and a password they choose, the room expires on a date you set, and you find out what they actually opened.
- Deal Rooms for investors: the model, the cohorts and the cap table in one place, with an expiry date.
- Onboarding Rooms for customers: a personalized room per account, holding the plan, the contract and the technical documents.
- Share Rooms for partners: co-marketing assets and joint pipeline documents, in a room you can close in one click.
- Grant a person or a whole company, and everyone linked to that company inherits access and loses it when they leave.
- Every visit, folder and download is recorded against a name, so you know what they read before you call them.
The agents
Five agents, five jobs, and a hard limit on all of them
None of these changes a field on its own. The Context Agent returns text and saves nothing to a field. The Research Agent hands back proposals a person accepts one at a time. The On-Task Agent reads your tasks and writes an email. The Project Context Agent offers tasks you accept or ignore, and the Proposal Agent hands back a draft you edit before anything is sent. We drew that line because an agent that reads the open web and writes to a relationship record will eventually write something false about a real person, and someone on your team should always agree before a field changes.
Context Agent
Where this relationship stands
Four sentences at the top of any contact, company or deal: what it adds up to, what moved most recently, and what is unresolved or waiting on somebody. It reads the fields, the notes, the text inside attached documents, the linked records and the activity history, and it does arithmetic on dates so it can say a close is eleven days out with the last contact thirteen days stale.
- It returns text, and it never writes to a field.
- It tells you when a record is too thin to be worth summarizing, instead of padding out an answer.
- It remembers what it already read, so opening a record twice only costs you once.
Research Agent
Fill the blanks, with receipts
Fills in what a contact or company record is missing: website, industry, size, location, title, the things you would otherwise look up by hand. It asks business data providers first, then the open web, and it can find a contact from a name and a company. Every value arrives with its source, and when it is not certain it says so.
- It proposes each field, and a person ticks it before it is written.
- Every value names the provider or the page it came from.
- Researching a company a teammate already researched costs you nothing.
On-Task Agent
What needs you today
Keeps the running answer to what is overdue, what is due, and which deals have gone quiet, on the home screen when you look and in one short email in the morning if you want it. The email is skipped entirely on days when nothing needs you, because a daily message that is usually empty is a daily message people stop opening.
- It runs off the same tasks and thresholds you can see and edit.
- One email, at an hour you choose, or none at all.
- It stays quiet on quiet days, on purpose.
Project Context Agent
The brief behind every project
Reads the statements of work, call transcripts, notes and contracts you put on a project and keeps one standing brief: what is settled, what nobody has answered yet, who owes what and by when. Each new document is read against the brief rather than the whole pile, and when you ask, it finds the work the documents imply and offers it as tasks.
- Every task it finds is a proposal, and nothing reaches the board until somebody accepts it.
- The brief stays a readable length, dropping what stopped mattering.
- Reading a document uses a few AI credits, and documents filed before the assistant could read them are read in the background at no cost to them.
Proposal Agent
Your contract, as a proposal
Upload the Word or PDF agreement you already send and it rebuilds it as proposal blocks: cover, scope, pricing, terms and signature, and where a block quotes a PDF, it notes the page. The pricing table is the deal’s own, so no number is retyped by hand or by the model.
- It hands back a draft, and you review every line before anything is sent.
- Word and PDF agreements both import.
- A PDF or text contract uses about 11 AI credits, and most Word files convert without using any.
Context building
The agents are only as good as what they read, so we made that the product
Anybody can put a language model in front of a contact list, so the difference is what the model has to work with. Storm OS turns everything you were already doing into context: the note you typed after the call, the contract somebody attached, who works where, and what has actually happened, all of it reachable by search and readable by the agents without a single tag.
- PDFs, Word files and text documents are read the moment they are uploaded, so search finds a clause inside a contract rather than a filename.
- Notes are just as searchable, which matters, because the sentence somebody typed after a call is the most valuable text on a relationship record and usually the hardest to find.
- Who this person works for, which deals they sit on, and who else is involved all count as context.
- Search results respect permissions exactly. You are shown a match only if you could already open the thing it is in.
- Scanned pages are named as scanned rather than reported as broken, because "there are no words in this" and "we could not read this" send you to two different places.
Your model, or ours
Yours to switch off, and yours to point somewhere else
The assistant is on from the first day, an admin can switch it off during setup or at any time after, and nothing is sent anywhere while it is off. We never train a model on your records, and Anthropic’s terms forbid it from training on what we send. Connect your own Anthropic key and each agent you move onto it runs on your account instead of ours and stops using your workspace’s AI credits. Two things stay on our accounts either way: the background reading of documents already filed on your records, which uses no credits, and research’s lookups with the data providers, which do.
- One switch under Settings turns every agent off for the whole workspace, and research has a switch of its own.
- Every plan includes AI credits each month for the whole workspace. A summary uses about 1 and researching a contact about 360.
- Bring your own key and the agents you move onto it stop using credits. OpenAI, Gemini and Grok are next.
- Thumbs up and thumbs down on every answer, with corrections that shape the next one inside your workspace and stay there.
- Sharing anything at all with us is a separate switch that starts off, and never includes a record, a name, or the text an agent produced.
Install it
Install it on your phone from the browser, with no app store
Storm OS is a progressive web app. Open it in a browser on your phone or your laptop, choose install, and the icon lands on your home screen next to everything else. It then opens full screen like any other app, works when the signal drops, and updates itself. There is no app store, no download, no review queue, and nothing to ask an IT department for.
- It opens full screen like any other app on iPhone, Android, Mac and Windows, and it is the same product everywhere, we built the phone version first and widened everything else from it.
- It keeps working when the signal drops. Your recent records live on the device, so they open in a parking garage and on a plane as reliably as they do on office wifi.
- Edits made offline are kept on the device and go up when you are back, with a small counter showing how many are waiting, and nothing is ever silently dropped.
- If two people changed the same record while you were away, you are shown the conflict rather than having one version quietly win.
- It updates itself the next time you open it, with no store review sitting between a fix and the person who needs it.
Security
Small team, serious security
Your workspace is walled off inside the database itself, a layer deeper than our app code, so another customer's data can never reach yours. You can sign out any device, every administrative action is written to a log nobody can edit, and a full export of your workspace is one click away.
Row-level security · rotating sessions · audit trail · full export
One platform, growing by modules
Relationships first, then the work around them
Storm OS grows as one system on one bill, and each new module lands on the records you already keep, so a project, a campaign, an invoice or a support case attaches to what is already there. Beta means a module is live in your workspace and still improving.
Storm Eye
Customers, investors and partners in one graph, the deals that move them, the proposals they sign, and the private rooms you share with them.
In the price
Storm Project
Internal or client work on a board or a calendar, reading its own contracts and transcripts so the brief stays current.
Included, no extra cost
Storm FinanceBeta
Invoices raised off the deal that promised them, sent in your name with replies coming to you, paid by card or however you already get paid.
Included, no extra cost
Storm MarketingBeta
Email designed and sent from your own domain to segments that build themselves, with every open and click landing on the records your deals live on.
Included, no extra cost
Storm Service
The support side of the relationship, in the same place as the deal, the project and the invoice. Licensed separately, arriving in November with a first group of beta customers.
November
Core is what you pay for. Everything marked included is a separate offering, and early access members get it at no additional cost for at least a full year.
What is coming, and when
- NovemberStorm Service for its first group of beta customers, and API access in private beta
- DecemberThe MCP server and the Workflow and Automation Studio, both in private beta
- Early 2027A Storm OS Zap, so Zapier can reach your relationship graph
Mailchimp, Stripe, Sign in with Google and Claude are connected today, and the rest of the list is on the integrations page.
Ready in fifteen minutes on your phone, we timed it.
Sign up, let Storm OS read your website and propose your brand, and your pipelines are ready in minutes. You start with relationship management best practices built in, plusfive agents that each do one job well. $24 a month, 5 users included.
No credit card to start · 30-day trial · Live and customized in 15 minutes