Follow one real task.
A few lines, a recent example and the tools you use are enough. Include a budget or deadline if you have one. We assess fit before asking for a detailed brief.
How we begin
A missed enquiry. Information copied twice. A task that stops when you step away. Start with the problem you have, even if it is small.
Describe the taskYour first note starts a conversation, not paid work. We agree scope, fee and delivery date before an invoice.
A few lines, a recent example and the tools you use are enough. Include a budget or deadline if you have one. We assess fit before asking for a detailed brief.
We say whether this calls for a repair, a connection or a build. You receive the result, boundaries, fee and delivery date in writing. Any paid investigation is agreed separately first.
Review it working, including what happens when something goes wrong. The handover covers the agreed source, access, operating note and responsibilities for ongoing care.
A focused first project
A visitor sends a request. The right person receives the details and can reply without retyping or searching. That is a complete first project in its own right.
Example boundary: one existing form, one destination and the reply path. A redesign, CRM migration or further workflows need a separate scope.
Connect the existing form to the agreed destination. Give the visitor a clear confirmation and the receiving person the original note and a usable reply address.
Follow a complete request, a missing detail, a repeated submission and an interrupted connection. Confirm what the visitor sees, what the team receives and who handles an exception.
The working change, agreed source and access, plus a short operating note: where requests arrive, how to test a delivery, what it costs to run and who to contact if it stops.
Useful after we leave
The handover should leave your team or another maintainer able to carry on. We agree that responsibility before the build.
The proposal lists custom source, data exports, account access and any third-party licences. You can see what transfers and what still relies on a service.
A record of providers, recurring costs, renewal dates, access owners and recovery steps stays with the business. Passwords travel through an agreed secure route.
Agree a handover check: the person taking over follows the instructions, makes a routine change and tests recovery in a safe copy. Unresolved steps are recorded.
Tell us the task and, if useful, your budget and deadline. We will say whether they fit the likely scope. The proposal names the fee, delivery date, access needed from you and any running costs. You decide whether to proceed. Extra work needs a separate agreement.
Yes. We first look at their interfaces and limits. If a setting or connection in a tool you already own solves the problem, that can be the first move.
We can begin there. The same principle applies: a defined audience, a clear visitor action and an agreed set of pages and connections. It does not need to become a larger software project.
Yes. We agree what can be shared. Your first note should be a broad outline, without client records, passwords or confidential documents.
You may maintain it yourself, appoint someone else or agree ongoing care with us. The proposal identifies ownership, recurring services, support and any limits before work begins. Ongoing care is a separate decision.
A short note is enough to start. We can work through the initial questions in writing.