How I work: from the first conversation to go-live
A simple approach, in steps validated together, so you always know where your project stands and what is planned.
The steps of a project
- First conversationYou tell me about your business, your needs and your constraints, by email and then a conversation.
- ScopingI restate the need, and we clarify what is a priority, what can wait and what is out of scope.
- Proposal and quoteYou receive a detailed proposal: scope, steps, deliverables, terms. Nothing starts before you agree.
- Step-by-step deliveryI move forward in batches, with regular check-ins. Each step is validated before the next one.
- AcceptanceYou test what has been built on your real cases; corrections within the agreed scope are made before go-live.
- Go-liveI set up the solution and hand over the access credentials and the delivered files.
What you get
- A written scope in the quote, to avoid misunderstandings.
- Regular check-ins on progress.
- Validated steps before moving on.
- A single point of contact, from start to finish.
- Simple explanations, without jargon.
- The agreed deliverables, handed over with the access credentials.
What I need from you
- A description of your need and context, even an imperfect one.
- The useful access (existing website, domain name, hosting, software concerned).
- Real examples: files, exports, pages you like.
- One person who validates the steps, within the agreed deadlines.
The framework of the services
Each service is delivered under an obligation of means: I apply my skills and the necessary care to reach the objective defined together. I do not promise a measurable result, such as a Google ranking or a sales volume, because it depends on factors I do not control.
Training, user support and maintenance are not included in the basic services. They can be covered by an additional contract, to be requested and subscribed separately (recurring services contract), drawn up on a quote basis.
Deposit and payment schedule. For a fixed-price project (a global price for a defined scope), unless the quote states otherwise: for an expected duration under one month, 50% at order (deposit) and the balance at acceptance; beyond that, 30% at order (deposit), 40% on delivery for acceptance testing and 30% at acceptance. For other billing modes, the schedule is set out in the quote. Deposit invoices are payable on receipt, others within thirty days.
Step validation deadline. From the delivery of each deliverable, you have ten business days to check it and report any non-conformity with the specifications in writing. Acceptance is declared by a signed report, with or without reservations; final validation triggers payment of the balance and go-live.
Ownership and licences of deliverables. Until full payment, you have a right of use limited to the needs of acceptance testing. After payment, the regime for bespoke developments is specified in the quote: exclusive assignment of economic rights, or a non-exclusive licence to use and modify. My pre-existing tools and components remain mine, with a licence of use to operate the deliverables; third-party components keep their own licences. Source code is handed over when the balance is paid. Details are in the general terms of service.
Frequently asked questions
How long does a project take?
It depends on the scope. An estimated timeline is included in the proposal, once the need has been scoped.
What if my needs change along the way?
Changes are discussed and priced before being carried out: the initial scope stays clear.
Can I follow progress?
Yes: regular check-ins are planned, and you validate each step.
How is the price set?
From the agreed scope, in a quote. See also the solutions and the contact page.
A project or a question?
Describe what you need in a few lines and I will get back to you to discuss it.