A salesperson on the road needs three things: what expires today, what a customer is worth, and whether an item is in stock. This app answers those three on six tabs, and the sales team behind it answers the rest in plain language.
fr.imachine.pragma.commercial · Android 8.0+ · Kotlin and Jetpack Compose · 9 business MCP tools · no public store: your instance serves its own build.
What it covers
Home opens on what presses: quotes that expire within seven days, customers whose buying rhythm slipped, and twelve months of revenue. Sales holds quotes, orders and invoices. Items carries the catalog with its stock per warehouse. Customers carries the book, each file with its revenue and its margin. Team is the conversation with the sales and order-admin agents. WIP holds the runs of that same team and the decisions they wait for.
The app writes as well as reads: changing the status of a quote goes through, under a confirmation. Any file — a quote, an order, an item, a customer — can be handed to the team with its context, so the question starts where you are.
The screens
Interface preview: the published screens are in English, the shipped app speaks French. A cross-team request is open to make the apps bilingual.
Home
Home — what needs you today. Quotes that expire within seven days, customers whose buying rhythm slipped, and the revenue of the last twelve months.
Team
Team — the sales and order-admin team. An empty thread shows what to ask, so the app needs no manual. The same team handles pricing and margin questions.
Sales
Sales — quotes, orders and invoices behind three segments, each with its own count. A quote whose validity runs out within two days is outlined in amber.Invoices — the unpaid total and the part older than thirty days. Each row says how many days it has been owed; a late one is outlined in amber.Quote detail — the lines, the total, the validity. Changing the status is read out loud and waits for a spoken "yes" or a tap: nothing commits on one gesture alone.Order detail — line by line, what was ordered, what shipped and what is left. A line with something left to ship is outlined in amber.
Items
Items — the catalog with its price and its stock. An item at or below zero is outlined in amber. Search matches the designation, the reference and the family.Item detail — stock per warehouse, twelve months of sales, and who buys it with the margin on each. The current month is drawn lighter: it is not over.
Customers
Customers — the whole book, searchable by name or contact. Tapping one opens its file with its revenue and its quotes.Customer detail — twenty-four months of revenue, the buying rhythm in days, what this customer buys most, and its quotes. "Talk to the team" sends the context along with the question.New customer — the name is the only field required. The form refuses a name already in the file and an address that is not shaped like an e-mail: the create button stays outlined until the refusal is gone.
Settings
Settings — opened by the gear on Home. The server, the installed version, and the newer build the app fetches from that same instance. The update button answers right under itself: up to date, version available, or release not found. Below, the model behind each worker of the team: tap one to move it to another backend. The same screen serves every business app of the shared module.
The WIP tab runs the screens of the shared module, bounded to this one team. They are shown on Pragma.
On your ERP, not ours
The app calls nine named MCP tools: quotes, orders, invoices, margin, customer activity, customers, products, sellables, stock. That list is the whole contract. Serve those names over your own ERP or database and the same screens run on your data, unchanged.
The figures on the screens are read, not computed on the phone: the buying rhythm, the margin and the twelve-month revenue come from the server, where the data lives.
The platform that serves those tools is described in MCP Infrastructure; the console that steers the teams in Pragma.
Nothing commits on one gesture
Marking a quote accepted is read out loud and waits for a spoken "yes" or a tap on the button. Without a microphone, the buttons decide alone. The app never changes a status because a voice sounded like a yes.