Run your business from your phone

Can you run a business from a phone? The short answer

Yes — for the daily job of knowing whether your business is healthy, a phone is enough, and you almost certainly have most of what you need already. The apps are on your home screen: Stripe's app shows payments, the App Store Connect app shows store sales once they clear reporting, and the MRR dashboards have mobile views. What a phone changes is not whether you can check — it is whether checking is worth doing. A screen you have to remember to open, that shows one number with no context, gets opened less and less until you are back to finding out about problems the next morning.

So the real question is not "can I see a metric on my phone" — you can — but "can I see enough, in one glance, to know if I need to act?" A payment app tells you money arrived, not that the customer who paid just hit an error using what they bought. An MRR app tells you the recurring number moved, not which customer moved it or why. Each app is right about its layer and silent about the rest, so answering "am I healthy?" means opening several and holding the answer together in your head.

We will get to the joined answer. But first the useful, honest part, because you can get a long way with tools you already have: the mobile options today, and where the line falls.

The mobile options today, named fairly

Before any joined platform, you can assemble a real mobile setup from apps you likely already have. Each does a genuine job on its layer, and for many businesses one is enough for a long time. Here is the honest map.

Stripe's mobile app

The default and the right first step for payments. Stripe's app shows charges, refunds, and disputes, pushes a notification when a payment clears, and gives a clean view of the day's takings from anywhere. If you take one thing from this section: turn its notifications on. It is free and immediate, and money arriving is the single most motivating signal there is. Its scope, by design, is the Stripe payment layer — it sees the charge, not the customer's error a minute earlier, and not the other rails your revenue runs on.

The App Store Connect app — and its reporting lag

If you sell on the App Store, the App Store Connect app puts Sales and Trends on your phone — useful for the shape of store performance, but worth being accurate about on timing. Those reports are delayed, often by a day or more, and proceeds are reported monthly, so a founder watching only the Connect app can wait a long time to confirm a sale happened. That wait is a real, searched frustration — and it is not Apple failing to provide data. Apple does emit a real-time signal through App Store Server Notifications v2 and StoreKit 2 transactions; it is the Connect reports that lag. A tool that ingests and verifies that signal can show you a purchase before the dashboard catches up. We cover exactly this in seeing app revenue in real time before App Store Connect catches up.

MRR dashboards on mobile

Baremetrics, ChartMogul, and similar tools turn raw Stripe data into the recurring picture — MRR, growth, churn — and most have a mobile view or app for checking on the go. For understanding the shape of a subscription business from your phone, these are purpose-built and genuinely good. Their focus is the revenue and subscription layer; they are not error monitors or product-analytics tools, and they generally see the processors they connect to rather than every rail plus the app behaviour around a customer. For the recurring number specifically, they are a strong mobile answer, and monitoring MRR goes deeper on watching the moves, not the daily total.

Error and alert apps

Your error tool probably has a mobile app that pushes exceptions, and you can pipe Stripe or other events into a chat app you already carry. Flexible and cheap — but the catch runs through this whole section: each is one more single-layer feed, and nothing joins them. You end up with a payments app, a store app, an MRR app, and an errors app — four true pictures of four layers, and a human doing the correlation between them.

Put together, these apps give you a workable mobile setup for free or close to it — start here. The question this guide answers is what you reach for when four apps on a home screen still cannot tell you, in one glance, whether you are healthy.

Why a pocket full of apps still can't tell you if you're healthy

The friction is not that the data is missing from your phone. It is that it is scattered across your phone. Each app is excellent at one layer and knows nothing about the others, so the moment a question spans two layers — and the questions that matter almost always do — you are app-hopping. A revenue number looks soft in the MRR app: cancellation, or a card that quietly failed? It cannot say which customer. You open Stripe, then the error app, and each answers only for its own layer. Three apps, three half-answers, and you still cannot say whether the morning is fine or on fire. That is not running your business from your phone; it is doing forensics on your phone.

The reason is structural, and it is the same one that shows up everywhere a business's data lives in separate tools: every app has its own notion of the customer — a charge, a store transaction, an aggregate, a session — and none of them is the customer. We mapped that fragmentation in full in the complete guide to real-time business monitoring. Mobile access does not fix it. It just puts the same disconnected layers in your pocket instead of on your desk.

What "healthy" actually needs: one identity-joined view

"Am I healthy?" is not a single-layer question, which is why no single-layer app can answer it. A strong revenue day with an error spike on your checkout is not healthy; a flat revenue day with everything working and customers happy might be. The health lives in the relationship between revenue, errors, entitlements, and the people behind them — and that relationship only exists once the layers are joined.

That join is the cross-match: Crossdeck joins revenue across rails, entitlements, errors, and analytics by identity, so a customer's scattered events collapse into one timeline. Once revenue and errors and behaviour resolve to the same person, "healthy" is something you see in a glance rather than assemble by hand. The failed payment is not an anonymous decline; it is a named customer on your top plan whose entitlement lapses tonight. The error is not one of a thousand; it is flagged because it struck someone who is paying you. The soft revenue number comes with the customer and the reason attached.

This matters even more on a phone than on a desk, because a phone is a glancing device. You do not want to run a five-app investigation from a bus stop; you want one screen that already did the joining, so a single look tells you whether to keep walking or to sit down and act. That same engine is what powers error alerts that name the customer: the difference between a number and a situation.

The whole dashboard, where you already are: Crossdeck on Telegram

A joined view is only useful if it reaches you where you already are. For most founders, that place is a messaging app that is always open — so Crossdeck delivers the whole dashboard to Telegram (@Crossdeck_bot), live today in private chat. This is not a cut-down companion to a "real" web app; it is the dashboard, joined, in the app you already carry. Four things run there now.

The Mini App: Home, Revenue, Errors, People

Tap into a Mini App inside Telegram and you get the full dashboard, with a bottom navigation across four views — Home for the at-a-glance picture, Revenue for the recognised numbers, Errors for the open issues, and People for your latest customers and signups. A project switcher moves you between apps if you run more than one. You sign in with Telegram, so there is no separate login and nothing extra to install. To be exact about what is shipped: this whole Mini App dashboard — all four views and the project switcher — is live today, not a preview. It is a full business dashboard that happens to live inside a chat.

The hard-data commands

When you want a number without opening anything, ask for it directly in the chat. /revenue returns this month's recognised revenue. /errors lists the open error issues right now. /people shows your latest customers and signups. /status gives business health at a glance — per project, the revenue this month, MRR, open issue count, whether any paying customers are affected by errors, and the last payment, with an "Open in app" button to jump into the Mini App. Every one of these returns live Crossdeck data — the recognised figure, right now — never an estimate or a guess. The figure is real, or it is not shown.

Proactive alerts that come to you

The best part of running your business from your phone is not checking — it is not having to. Crossdeck's alerts come to you: a sale, a failed payment, a new customer, and error alerts that carry the failing request, how many events and users are affected, an "In plain English" explanation of what broke, and a Mute button you can tap from the notification. Noise is filed automatically, and severity is graded so the loud ones are rare and mean something. The bot also watches pipeline health against a baseline — flagging, say, event ingestion going silent for a few minutes against its normal rate — so a problem that would never trip a revenue or error threshold still reaches you. The things worth knowing find you. For the step-by-step, getting Stripe error alerts in Telegram is the setup guide.

Prism: ask in plain English

Sometimes a glance raises a question you would rather ask in words than dig for. With /prism, you ask a follow-up in plain English — "which customers on the top plan hit an error this week?" — and get an answer off your live Crossdeck data. The detail that makes it trustworthy: Prism runs on your own connected AI model, with your own key. Crossdeck does not run AI on your data or train on it. You connect a model once in the Prism tab, and from then on your model reasons over your live numbers. It is not zero-setup — the connection comes first — but once it is done, your whole business is answerable in a sentence, from your phone. The natural-language side has its own guide in asking your business data in plain English.

One honest note on scope: all of this runs in private chat by default, with single-use tap-actions on the alerts. Shared team and group chats — where a whole team gets the same alerts and asks Prism together — are on the roadmap, not shipped yet. What is live now is the complete single-operator loop: the Mini App, the commands, the proactive alerts, and Prism. That is enough to run your business from your phone.

Separate apps you check vs one view that comes to you

The real difference is not "web dashboard versus mobile app" — both are things you have to remember to open. It is between a set of single-layer apps you check one at a time, and a single joined view that comes to you and answers across layers. Here is the contrast, plainly.

This is the moat, stated as plainly as we can: a phone full of dashboards tells you a handful of numbers; a joined view tells you whether you are healthy — because it holds revenue, errors, and identity in one hand. The single-layer apps are not wrong; they are right about their layer. Joining those layers by identity is simply the thing none of them was built to do, and it is what turns a phone from a place you run investigations into a place you run your business.

A morning check, from your phone

Here is the whole thing in one illustrative sequence — invented customer and numbers, but the exact shape of how a joined phone check plays out.

You wake up and glance at Telegram. No alerts overnight, so you already know the important answer: nothing crossed a line while you slept. You send /status anyway. It comes back per project: revenue this month, MRR, a couple of open issues, a green line that no paying customers are affected by errors, and the last payment a few hours ago. Thirty seconds, one screen, and you know you are healthy. You put the phone down.

An hour later, an alert arrives. Not "a payment failed," but: a renewal on your top plan just failed on a declined card, for a long-standing customer, and their entitlement lapses tonight unless it recovers. The alert already carries who, why, and what is at risk — because the revenue event, the customer identity, and the entitlement are joined. You read it once and understand the whole situation, from a queue at a coffee shop.

You want a little more before deciding. Rather than opening four apps, you reply with /prism: "has this customer hit any errors this month, and what's their usage trend?" Your own connected model answers off your live data: no errors, usage steady until this week, then a drop that lines up with the failed renewal. That is a customer worth a personal recovery email, not an automated dunning sequence — and you knew it in two taps, without a laptop and without correlating anything by hand.

How to start

Start free with what you have, then add the join when the app-hopping bites. A sensible order:

1. Turn on the free mobile notifications today. Stripe's app, the App Store Connect app if you sell on the store, your error tool's app. It is real and costs nothing — do not wait for something fancier to begin.
2. Add an MRR view on mobile. An MRR dashboard's app or mobile web for the recurring shape, so you are watching moves, not just the daily total.
3. Notice the app-hopping. The first time you open three apps to answer "who was that and is it a problem?", you have outgrown a pocket of single-layer apps.
4. Bring it onto one timeline, in Telegram. Join revenue, entitlements, errors, and analytics by identity, and route the alerts, the Mini App, the commands, and Prism to the chat app you already carry — so one glance answers whether you are healthy.
5. Connect a model for Prism. For plain-English answers, connect your own AI model with your own key in the Prism tab once. After that, your whole business is answerable in a sentence from your phone.

The through-line is simple. Running your business from your phone was never blocked by mobile access — the apps have been there for years. It was blocked by the layers being scattered, so a phone could show you five numbers but not tell you if you were healthy. The join closes that gap: one view that already did the stitching, delivered where you already are, so a glance is enough. See how the cross-match works on cross-deck.com, ask your own numbers a question with Prism, or start free and wire the first joined alert into Telegram today.

Frequently asked questions