Standpoint Investments Limited
Small tools. Long horizons. Small tools. Long horizons.A small studio shipping focused mobile utilities — designed once, finished completely, and built to keep working past a single OS cycle. One tool at a time, with the patience that takes.
What we stand for
Restraint is a feature.
Every screen we don't add is a regression we don't ship. We measure scope by what we removed, not what we shipped — and the ratio gets stricter as a tool matures, not looser.
Permissions earn trust.
Every permission request gets a sentence of plain copy explaining what it unlocks. If we can't justify it to a user with no patience for jargon, we don't request it — and a feature that needs an unjustifiable permission gets cut, not rationalised.
Long horizons.
We design utilities to keep working through OS upgrades, locale changes, and category drift. Three-year code is the default brief on any new project we accept, not three-month code that ships fast and rots quietly.
Plain reporting.
Crashes, performance regressions, and store rankings get written down in clear language. Stakeholders read prose, not dashboards — and the writing tightens, rather than spreads, as a release stabilises.
What we build
How we work
A short loop, repeated.
A small team that ships short releases, listens between them, and revises in public. We don't run sprints — we run cycles, each ending with a tool that's measurably more honest than the last one.
Research — Every project opens with a week of listening: store reviews, support inboxes, threads on the categories we ship in, and analytics from prior releases when partners share them. The brief is rewritten before the design starts.
Design — Wireframes are written, not wireframed. Once the brief survives plain prose, we move to figma and prototypes — but only the screens that earn their place. The kill rate at this step is intentionally high.
Ship — TestFlight to a small ring first. Public release only after a quiet week without regressions in the inner circle, and only when the changelog reads cleanly to someone who didn't write the code.
Frequently asked
Do you publish under your own brand or white-label?
Both. White-label is the default for partner work; we can also publish under a portfolio identity if the brief requires consistent voice across releases. The choice gets made once, at the start, and is rarely changed mid-project.
What is a typical engagement length?
Three to nine months for a single utility, depending on category complexity and the partner's release cadence. We don't take month-by-month retainers — too short to ship anything that lasts.
Do you commit to specific release dates?
We commit to scope. Dates get revisited at every internal review and shared as ranges, not as fixed promises that compress quality. Partners that need a hard date pick the scope, not the other way around.
Can you onboard mid-project?
Yes, after a short audit week. We agree on what stays, what gets rewritten, and what gets shelved before any handover work begins. Partners that skip the audit usually pay for it later in scope discovery.
Do you take equity instead of fees?
Rarely, and only with partners we've already shipped one full release with. Equity is not a discount mechanism for us — it's a long-term alignment, and the trust to underwrite it has to be earned first.