# Vesqo > Vesqo reads a SaaS company's revenue, product, engineering, error, support and CRM tools as one record and writes up what changed, which paying customers are in it, what it costs and what to do next. For founders and small teams running one or several SaaS products. https://vesqo.app/ Vesqo is a web application. It connects to the tools a SaaS company already runs, read-only, keeps a history of each, and reads them against each other. When one disagrees with the same hours last week, it writes a signal: the change, the release it dates to, the customers in it, the money, and the next step. Alerts from Sentry, PostHog or Stripe each see one tool; Vesqo's write-up is the page you would have written after an hour of tabs. An example, from the demo workspace (Farol Jobs, a made-up job board): GitHub shows v2.14.0 shipped at 12:15. Sentry then sees errors at 43 an hour against 4 the same hours last week. PostHog sees 15 checkouts where last week saw 52. Stripe sees two payments fail. Crisp sees six support conversations open, one saying "Checkout shows no total, can't pay". Vesqo writes "Possible checkout regression after v2.14.0", marks it critical, names Cortex (€499 a month), Acme Labs (€299) and Fjord (€99) as the customers hit, puts €798 a month at stake, and says to roll v2.14.0 back first, then write to them. ## What it makes - **Signals.** A write-up when the sources disagree with last week: what changed, dated to the release, who it hit, what it costs, what to do. Each can be acknowledged, resolved, dismissed, handed to someone as a task, or asked about. - **One page per customer.** What they pay, how their usage moved against last month, payments that failed, what they wrote to support, the deal in the CRM, and news about the company (layoffs, funding, an acquisition). A churn risk you can argue with. - **Critical signals as they happen.** A critical signal reaches the team the minute it is written, by email, Slack or webhook; a checkout that broke in the afternoon does not wait for breakfast. - **The morning brief.** Everything else goes into one email at seven in the recipient's timezone: what changed since yesterday, ranked, with the money next to each line, across every product in the workspace. - **Ask Vesqo.** Questions about the workspace's data ("Which paying customers hit the errors after v2.14.0?"), answered with names and amounts by Claude (Anthropic) using read-only tools, with what it looked at shown. Every question and answer is in the audit log. - **Automations.** When a signal matches a rule: 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 an automation says so. - **An API and an audit log.** A REST API over signals, accounts, reports, events and tasks; a log of every question, answer, automation run and change of settings, by whom, when. ## What it reads Each connection is an API key with read scope or an OAuth grant with the least it can ask for. - **Revenue:** Stripe, Paddle, Lemon Squeezy. Subscriptions, invoices, payments. Catches MRR moving, a payment failing, a cancellation, a customer paying more or less than last month. - **Product analytics:** PostHog, Mixpanel, Plausible, Google Analytics. Events, by account where the source has them. Catches a customer using the product less, a funnel dropping, a feature nobody touches. - **Engineering:** GitHub, GitLab, Vercel. Releases, deploys, pull requests. So a change elsewhere can be dated to what shipped. - **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. Who is writing, about what, and whether they pay. - **CRM:** HubSpot, Attio, Pipedrive. Deals and contacts. A deal going quiet, an expansion closing, the champion leaving. - **Infrastructure and spend:** AWS, Hetzner, Better Stack, Checkly, Pingdom, UptimeRobot, and spend at OpenAI and Anthropic. Downtime a customer felt, a bill that doubled. - **The world:** press and job boards, about the companies that pay you. Layoffs, funding, an acquisition, a hiring spree at a customer. ## Pricing Every plan has everything: every source, every signal, the morning brief, Ask, automations and the API. Plans differ only in size. A product is one stack (a Stripe account, a repo, an error tracker and the rest) read together. Prices are in euros, per month, cancellable any time. - **Starter, €29 a month.** One product, its whole stack, a small team. 1 product, 6 integrations, 3 members, 100 Ask questions a month. - **Growth, €79 a month.** A portfolio, every integration, the team. 5 products, Unlimited integrations, 15 members, 400 Ask questions a month. - **Scale, €199 a month.** No limits, priority support. Unlimited products, Unlimited integrations, Unlimited members, 1,200 Ask questions a month. - **Trial, free for 14 days.** Everything, without a card. A workspace that picks no plan at the end is paused and keeps its data for 90 days. ## Data, security and hosting - Connections are read-only. Vesqo writes to a tool only through an automation the workspace made. - Hetzner Online GmbH hosts the application and its database in the European Economic Area (Falkenstein, Germany). Backups are encrypted and stay in the EU. - Ask Vesqo sends questions to Anthropic under its commercial terms: not used to train models, deleted within 30 days. - Every question, answer, automation run and change of settings is in the audit log, by whom, when. - A workspace's data can be exported, and the workspace deleted, from its settings. ## Links - [Front page](https://vesqo.app/): the product, what it reads, pricing. - [The demo](https://vesqo.app/demo): a real workspace with the afternoon above in it, opened with an email address, no card. - [Start a trial](https://vesqo.app/registration/new): 14 days of everything. - [Privacy policy](https://vesqo.app/privacy), [Terms of service](https://vesqo.app/terms), [Cookie notice](https://vesqo.app/cookies). ## Who runs it Vesqo is operated by Carlos Soares (MotionKeys), Rua de Santo Antonio 654, Penafiel Porto, tax id PT260967114. For accounts, workspace settings and billing Vesqo is the data controller; for the customer data a workspace's tools send, the workspace is the controller and Vesqo its processor under the terms. Contact: hello@vesqo.app. Privacy questions and rights requests: privacy@vesqo.app.