main clause you tell us
Tell us, in one sentence, what has to happen out on the job,
and Vistara Software will unfold it into an app that keeps working without signal, plus a small tool for whoever plans the day. We build for UK businesses whose work happens on a bench, at a gate, in a van or up a stairwell, and at the end you own the code, the store accounts and the data.
Write your sentence Watch one unfold
Sent one already? Your client room keeps every brief you file while signed in, and shows which of the eight stages it has reached.
clause we take it apart
and we take it apart into the screen it needs:
A sentence about work already holds most of a design. Its nouns are the things that get written down: a piece, a count, a room. Its verbs become the buttons. Its before the trailer leaves or on Friday is the moment the app has to remember for you.
Watch three ordinary sentences come apart into working screens. The signal bars stay empty on purpose: everything is kept on the phone until there is somewhere to send it.
What a sentence leaves out is just as useful. It rarely says who checks the work, what happens when two people disagree, or how long anything must be kept. Those gaps are where the questions start.
The three sentences, as text
- Each piece gets measured twice and signed off before finishing. The piece becomes a field, the two measurements a list, and signing off a button.
- Count the stock at the gate before the trailer leaves. The count becomes a field, the gates a list, and the trailer leaving a button.
- Cleaners tick every room, and the report goes out on Friday. The rooms become a list to tick, the cleaners a field, and Friday a button that queues the report.
clause we ask first
we ask the people who do the work before anyone draws a screen,
Ninety-nine in every hundred UK businesses employ fewer than fifty people, and three in four employ nobody besides their owners: 4.1 million of the 5.6 million private-sector businesses counted at the start of 2026. A great deal of that work happens away from any desk, and a great deal of it is still organised on paper, in spreadsheets and in message threads that one person fully understands.
Department for Business and Trade, Business Population Estimates 2026
So discovery starts where the work does. We talk to the people doing it, go through how it runs today, list every piece of information it touches and every way it can go wrong, and agree in writing what is in, what is out and what “done” will mean.
- Who does the work, and who checks it?
- Where does it happen, and how much signal is there?
- What do the paper, the spreadsheets and the threads say today?
- What must never be lost, even if a phone is?
clause we sketch, then build
sketch it where they can touch it, then build it in slices,
Before any code is written, the screens become a clickable prototype that the people doing the work tap through on their own phones. Whatever confuses them is redrawn, not explained.
Then the real software is built in short increments. Each one ends with a demonstration of something that works, and what comes next is decided with you rather than for you. You can open the latest build on your own phone after every slice, and anything that turns out to matter less than everyone thought can simply stop being built.
- One sentence a shared statement of the problem
- Discovery a scope, a list of the data, the risks, what done means
- Prototype screens everyone has already touched
- Each slice software that works, shown working
clause it keeps going
make it keep going when the signal goes,
A farm gate, a basement plant room or a site with one flickering bar cannot wait for the network, so the apps are built local-first.
And the rule for two people editing the same job apart is written down and agreed before anyone needs it. These are the rules we propose to start from:
- A status that only moves forward the furthest step wins
- Notes keep both versions and ask
- Counts add the changes together, never overwrite
- Photos and signatures attached to the job, never replaced
Each project agrees its own rules during discovery, because the right answer depends on the work.
clause we test
test it against the eye and the hand that will use it,
We design and test to WCAG 2.2 level AA, the W3C accessibility guidelines published in October 2023: with a keyboard alone, with the screen readers built into phones and computers, for colour contrast, and for the size of every tap target. Mobile security checks are aligned with OWASP’s Mobile Application Security Verification Standard: how data is stored on the phone, how it travels, and what the phone’s platform is trusted with.
We also test on old, cheap phones as well as new ones, with the signal pulled out in the middle of a save, and with two edits made apart to the same job. Every change is read by a second developer before it is merged, every release is signed, and the components inside the app are listed so they can be checked when a weakness is published.
final clause you keep it
and hand you all of it — code, accounts and data — to keep.
Small firms say switching software feels too risky and worry about being locked in; the government’s SME Digital Adoption Taskforce recorded both in its final report in July 2025. Our answer is a handover that leaves nothing behind with us:
- The code repository moved into your own account
- The app listing published under your own developer account
- Every password and key rotated, so none of ours works any more
- A runbook how to build it, release it and recover it
- Your data exported in an open format
After that comes an agreed support term with security updates and a published way to report a vulnerability. If support is ever going to end, you hear at least a year before it does, which is what the UK’s Software Security Code of Practice asks of suppliers. Software that is retired goes with notice, an export and a plan for its listing.
None of this needs our permission later. The accounts are yours from the first day, so another studio, or your own staff, can pick the work up whenever you choose.
punctuation the full stop
Full stop.
Vistara Software is VISTARA SOFTWARE LTD, a private limited company registered in England and Wales. The address below is its registered office. Work is done remotely, and sessions in person in London can be arranged.
- Legal name
- VISTARA SOFTWARE LTD
- Company number
- 17431091
- D-U-N-S
- 235119012
- Registered office
- Office 1880 60 Tottenham Court Road, Fitzrovia LONDON, W1T 2EW United Kingdom
- Jurisdiction
- England and Wales, private limited company
- Incorporated
- 1 September 2026
- Nature of business
- SIC 62012 Business and domestic software development