Technical discussion
Identify the options for a specific technical problem and understand potential trade-offs.
Quoted individually
- Initial problem review
- Suggested next steps
- Optional written recap
THREE ENGAGEMENT TYPES
Choose the scope before discussing the price
There is no fixed price grid published here. A useful estimate requires a description of the work, its complexity and the expected outputs.
Focused delivery
Build or adjust a clearly specified feature for an agreed outcome.
Quoted individually
- Feature definition
- Build and testing
- Agreed files and handover
Supported learning
Learn through relevant practical examples at a suitable pace.
Quoted individually
- Starting level and goals
- Guided demonstrations
- Agreed learning material
ESTIMATING
What a proposal should explain
- Target outcome and deliverable
- Included work and exclusions
- Timeframe and review stages
- Responsibility for third-party hosting, APIs and licences
External subscriptions are not assumed to be included and should be identified separately where relevant.
COMMON QUESTIONS
Before commissioning work
Can the engagement be small?
Yes. A well-defined question or small adjustment may not require a larger project.
Are software subscriptions included?
No. Hosting plans, software licences and usage-based services require explicit agreement.
What happens if the requirements change?
Changes should be reviewed for their effect on delivery, timing and price.
Have a problem worth solving?
An initial description is enough to explore what kind of technical support would be useful.