What happens after you contact me?
We start by discussing what you need, what already exists, and any deadline. I then identify the access or discovery work needed to define a scope. You work directly with me throughout the engagement.
Start a project conversation1. Describe the need
For an existing site, send the public address and a description of the problem. For a new application, explain who will use it and what they need to do. Do not send passwords, private records, or production data through the contact form.
2. Review enough detail to scope the work
A small, clear repair may be straightforward to define. An unfamiliar application or a complex new build may need a paid assessment or discovery stage. We agree on that scope before work begins.
For inherited applications, the review can include the repository, hosting, database, integrations, and deployment process. For new work, it focuses on workflows, data, users, and acceptance criteria.
3. Agree on deliverables and responsibilities
The agreement defines the work, pricing approach, review points, access, ownership, and responsibilities. Any estimates depend on the information available and the assumptions recorded. Changes to scope need to be discussed rather than silently absorbed.
4. Review progress in working software
We agree on a review cadence and use demonstrations or a test environment to check the result. Feedback can expose missing requirements before they become expensive to change.
5. Test and deploy
The checks depend on the change: forms, integrations, payments, data migration, background jobs, and other important workflows may need different tests. Deployment planning includes backups, access, rollback, and any maintenance window.
6. Agree on support after delivery
Source-code access, hosting accounts, documentation, and support responsibilities should be clear. Ongoing maintenance is a separate scope when it is needed; response expectations are agreed for the engagement.
Who owns the code?
Ownership and licensing are defined in the engagement agreement before development starts. Third-party components may have their own licenses.
Can we discuss confidentiality first?
Yes. Let me know before sharing confidential information so we can discuss the appropriate agreement and access arrangements.