A defined objective
For a feature or work package whose expected result we can define. The scope, price and acceptance criteria are agreed before work begins.
Your application is already online. I help you regain an understanding of it, fix problems and organise the next improvements.
A changing provider, recurring bugs or a growing backlog? I work with SMEs and software publishers as a direct technical point of contact.
You introduce your project, the people who use the application and what you would like to improve. It is also an opportunity to get to know each other.
We discuss a way of working suited to your needs. I set out the proposed scope, deliverables, billing model, budget and schedule.
We agree on the proposal before starting work.
When a review of the existing application is needed, it provides a basis for choosing the first tasks. Its scope, deliverables and reporting format are set out in the proposal.
The assessment does not automatically commit you to maintenance. We decide what comes next based on its findings.
Application maintenance covers the agreed fixes, updates and improvements. Support can be provided at a fixed price, on a time-and-materials basis or through a combination of both.
For a feature or work package whose expected result we can define. The scope, price and acceptance criteria are agreed before work begins.
To reserve development time and work through a list of requests. Billing is based on time spent, at the agreed rate and volume.
For example, one maintenance day per month billed by time spent, with new features at a fixed price. The frequency and included work are adapted to your needs.
We prioritise requests and review completed work. Changes are documented to make handover easier. Any request outside the scope is discussed before work starts; hosting and deployment responsibilities are defined together.
I support Robin Pandikian, a magician and mentalist, in managing his website. I also answer his questions about his Google Business Profile and web strategy: one point of contact for technical support and everyday decisions.
Read about this support in my referencesA takeover can be considered using the available resources, even without a direct handover. Gather what you have: code repository, service accounts, documentation or hosting contact details. If something essential is missing, we determine what must be recovered before proceeding.
My specialities are React, Next.js and Java. For another environment, describe it in our first conversation: I assess whether I can help before proposing an engagement.
Support hours, response times and arrangements during absences are agreed before any ongoing commitment. Continuous on-call support is not included by default.
Describe your project and objectives in a few lines to arrange an initial conversation. If you have a deadline, include it.
Opens your email application. You can also use the contact page.