Yes. Your app is published under your own firm’s name to both the Apple App Store and Google Play, carrying your colour, type and logo. Clients download your firm, not ours.

They match because they are the same numbers. Every screen reads a governed metric you have already defined, so a client’s balance, an advisor’s book and the figure in a board pack all come from one definition rather than a nightly copy that drifts. There is no second data model to reconcile.

Access is enforced at the data layer through row-level entitlements, not hidden in the interface. A client is scoped to their own household. An advisor is scoped to their own book. The filter is applied before a query ever returns a row, so a mis-built screen cannot expose data the viewer is not entitled to see.

Usually the same day. Pages, metrics and menus are yours to edit, and adding a screen does not require a release or a place in someone else’s roadmap. A firm that decides on a new view in the morning can have it live for clients that afternoon.

No. There is a page builder for the screens, a metric builder for the numbers, and menu management for what each role sees. If you would rather not click through an interface at all, Milemarker’s MCP server exposes pages, metrics and menus to the AI assistants your team already uses, so you can describe the change in plain language and have it made.

They can act. Requests, approvals and signatures run through the workflows your firm already operates, so something started on a phone lands in your real process rather than an inbox. New accounts can be opened with Goldman Sachs from the app, prefilled from data you already hold and validated before submission.

It reads the data platform you already run — custodial feeds, CRM, accounting and planning — reconciled before anything reaches a screen. Milemarker Mobile is not a separate integration project stitching logins together; it is a surface on data your firm has already governed.

If your firm already runs on Milemarker, most of the work is behind you — the data is reconciled, the metrics exist and the entitlements are in place. Launching is then a matter of designing the screens, setting menus for each role, provisioning users and publishing the listing. Firms starting from the data work should expect that to be the longer part.

Yes, and this is the point of it. Menus are set per role, so a client, an advisor and an operations lead open the same app and get a different set of tabs built for the job each of them is doing. You maintain one app rather than three, and you change the menus yourself.

As current as your custodial feeds. Balances and activity refresh with each load, so a client checking their portfolio sees this morning’s position rather than last month’s statement. Nobody on your team has to publish or push anything for that to happen.

Entitlements are enforced in the warehouse rather than in the app, which is the meaningful difference. A client user is scoped to a single household by policy, so even a mis-built screen returns nothing they are not entitled to see. Account numbers can be masked, and sensitive fields anonymised, before they ever reach a device.