Applications
What is an application?
In Statement, an application is a saved, reusable piece of financial work - a dashboard, a report, or an automation, that you built once, in plain language, and that keeps working going forward. Instead of re-asking the same question every week or rebuilding the same report every board cycle, you turn it into an application and it's just there, kept up to date automatically. Think of it as the difference between asking a question and building a tool. Asking Statement "what's our AR aging" gets you an answer right now. Turning that into an application means anyone on your team can open it any time and see the current answer, without re-asking.
How applications differ from dashboards
A traditional dashboard is built by someone with dashboard-building skills, using a fixed set of widgets, connected to a fixed set of data sources. Changing what it shows usually means going back to whoever built it. A Statement application is built by describing what you want in plain language, and it's connected to the same reasoning layer that answers your ad hoc questions - so it isn't limited to whatever widgets existed at build time. You can ask for a change the same way you asked for the application in the first place: by describing it. Imagine your team uses a monthly revenue dashboard with a trend chart and a table of totals. It answers a familiar question: “How much revenue did we earn?” A Statement application can start with that same view, built by describing what you need in plain language. For example, you could ask: “Build a revenue app using our Stripe data, with monthly totals, a comparison with the previous month, and a short summary.” Statement retrieves the relevant data and creates a saved application with those charts, figures, and explanations. As your needs change, you can ask Statement to update the app: “Add a breakdown by customer” or “Make the summary shorter.” It uses the existing app as the starting point and retrieves additional data when the change requires it. You can return to the app, refresh its data, and schedule recurring updates. The practical difference is how you build and maintain the view: you describe what you want to understand, then refine the application through conversation.