A first conversation
Book a free 15-minute call with me. Describe the job, the people using the app and what needs attention. You can use made-up examples; account access and private information come through an agreed route later.
Review or pilot
For an existing app, we agree a review of the code, accounts, data and provider connections. For a staff assistant, a small pilot can test approved sample documents and useful questions. The scope and cost of this early work are explicit.
Write the service plan
The proposal names the application, suppliers, account ownership, data flow, usage arrangements and responsibilities. Setup or migration work, continuing management and third-party charges are identified separately. Support hours and recovery needs are agreed here too.
Test the promised behaviour
The checks reflect the setup. They may include sign-in and restricted retrieval, document updates/removal, missing answers, provider failures, rate limits, budget behaviour, backups and restore.
A multi-customer app needs isolation tests for those customer boundaries before it is treated as ready.
Launch with a way back
We agree access, release steps, checks after switching and a fallback where appropriate. The handover identifies the accounts, operating notes and people responsible. A prototype showing an answer is only one part of the launch decision.
Run and review
Monitoring, updates, usage and service changes follow the written scope. We agree how issues are raised and who acts. Changes in workload, provider terms or business needs can require a revised arrangement.
Start with the setup
you actually need.
We agree what to investigate, what to test and what the continuing service covers. Any paid work is agreed before it starts.
Let’s look at
your setup.
Tell me what you want the app to do, or what needs attention. We can work out the next step together.
Book a short callOr send me the outline