Critical, the minute it is written
By email, Slack or webhook. A checkout that broke at three in the afternoon does not wait for breakfast.
Know what broke, who it hit,
and what it costs.
Everything happening in your SaaS, without opening every tool. Vesqo is a business observability tool for SaaS companies: it reads Stripe, PostHog, GitHub, Sentry, support and CRM together and writes up what changed, which paying customers it hit, and what it costs. When they disagree with last week, it writes the page: the release, the customers, the euros, the next step.
For founders and small teams running a SaaS, with the tools and not the data team. The demo is a real workspace with a bad release in it; trials need no card; every connection is read-only.
19 September, Farol Jobsthe demo workspace
- GitHub
v2.14.0 shipped to production.
- Sentry
Errors at 43 an hour, against 4 an hour last week.
×10.5 - PostHog
15 checkouts completed since the release, where the same window last week saw 52.
−71% - Stripe
2 payments failed, Acme Labs and Cortex.
€798 - Crisp
6 conversations opened, where that half hour usually sees none.
×26Checkout shows no total, can't pay.
VesqoCritical95% sure
Possible checkout regression after v2.14.0
Hit Cortex (€499 a month), Acme Labs (€299) and Fjord (€99). Cortex and Acme Labs both tried to pay and could not: €798 a month at stake. Roll v2.14.0 back first, then write to them.
The write-up, not the alert.
Sentry saw the errors. PostHog saw the checkouts. Crisp saw the chats. Stripe saw the failed payments. None of them saw the release, or each other. Vesqo read all four against the same hours last week, dated the change to v2.14.0, and named who it hit. The page it makes is one you can act from: ask about it, give someone the task, or mark it done.
Open the demo
One page per customer.
Before the renewal call: what Cortex pays, how much less they use you than last month, the payment that failed, what they wrote to support, the deal in HubSpot and the layoffs in the news. A churn risk you can argue with.
Ask the follow-up.
Which paying customers hit the errors after v2.14.0? Vesqo reads the same tools, answers with names and amounts, and says what it looked at. Every question and answer sits in the audit log.
What it reads, and what it catches.
Connect what you have: each connection is a key with read scope or an OAuth click, and the connect page says what it needs. Vesqo keeps a history of each source and reads them against each other, so a change in one is dated to a change in another.
Revenue
Stripe
Paddle
Lemon Squeezy
WooCommerce
Subscriptions, invoices, payments, refused card attempts, the provider's fees.
Catches
MRR moving, a payment failing, a cancellation, a customer paying more or less than last month, stolen cards being tested against the checkout, Stripe's fees jumping.
Product
PostHog
Mixpanel
Plausible
Google Analytics
Events, by account where the source has them.
Catches
A customer using you less, a funnel dropping, a feature nobody touches.
Engineering
GitHub
GitLab
Vercel
Releases, deploys, pull requests.
Catches
What shipped, and when, so a change elsewhere can be dated to it.
Errors and metrics
Sentry
Bugsnag
Rollbar
Honeybadger
Datadog
New Relic
Prometheus
Issues and rates.
Catches
A regression, timed against the release and read with the checkouts.
Support
Crisp
Intercom
Help Scout
Zendesk
Conversations.
Catches
Who is writing, about what, and whether they pay.
CRM
HubSpot
Attio
Pipedrive
Deals and contacts.
Catches
A deal going quiet, an expansion closing, the champion leaving.
Infrastructure
AWS
Hetzner
Better Stack
Checkly
Pingdom
UptimeRobot
OpenAI
Anthropic
Uptime, and what you spend.
Catches
Downtime a customer felt, a bill that doubled.
The world
- PPress
- JJob boards
About the companies that pay you.
Catches
Layoffs, funding, an acquisition, a hiring spree at a customer.
When you want it to do something with what it found, an automation can open the issue in Linear, Jira or GitHub, post to Slack or Discord, or call a webhook. Nothing is written back to a source unless you set that up.
The urgent now. The rest at seven.
A critical signal reaches the team the minute it is written. Everything else goes into one email in the morning, and the rest of the day is quiet.
One email at seven, in your timezone
What changed since yesterday, ranked, with the money next to each line. Across every product you run, so one morning covers the portfolio.
Farol Jobs, Saturday15 signals
- €5,988
Renewal risk: Cortex renews in 25 days, one payment failed, five support threads.
- −74%
Cortex is using Farol Jobs less: 514 events this month against 1,941 last.
- €798
Possible checkout regression after v2.14.0: errors ×10.5, checkouts −71%.
- €12,000
Deal at risk: the Acme Labs expansion closes in 30 days, and a payment failed this month.
Read-only connections
API keys with read scope, or OAuth with the least it can ask for. Vesqo writes to a tool only through an automation you made.
Hosted in the EU
The application and its database run at Hetzner in Falkenstein, Germany. Backups are encrypted and stay in the EU.
Not training data, and an audit log
Questions go to the AI provider under its commercial terms: not used to train models, normally deleted within 30 days. Every question, answer, automation run and change of settings is logged, by whom, when.
Every plan has everything.
Every source, every signal, the morning brief, Ask, automations and the API, whichever you pick. Plans differ only in size: products, integrations, seats and Ask questions a month. A product is one stack, a Stripe account, a repo, an error tracker and the rest, read together.
Starter
One product, its whole stack, a small team.
€29a month
- 1 product
- 6 integrations
- 3 members
- 100 Ask questions a month
Growth
A portfolio, every integration, the team.
€79a month
- 5 products
- Unlimited integrations
- 15 members
- 400 Ask questions a month
Scale
No limits, priority support.
€199a month
- Unlimited products
- Unlimited integrations
- Unlimited members
- 1,200 Ask questions a month
The trial is fourteen days of everything, without a card. Pick a plan at the end, or don't: a workspace without one is paused, and keeps its data for 90 days in case you come back; then it is deleted. What a product is, and what happens at each limit.
See what it finds in a workspace with a bad afternoon in it.
The demo is Farol Jobs, the afternoon above, every screen open. Ask it anything. Then connect your own.