Hire me for the
build, not the meeting.
I take a small number of fixed-scope engagements alongside Skolvo. You get a written scope with milestones and a price before anything starts, something running in your hands every week, and source code in your own repository at the end. If software is not the right answer to your problem, I will tell you on the first call rather than quote you for it.
- Basis
- Fixed quote per scope
- Cadence
- Weekly drops, not one reveal
- Typical size
- 2 to 10 weeks
- After launch
- Two weeks of support included
- S-013–8 weeks
Mobile & web product build
One codebase, both platforms, shipped to the stores — Flutter for mobile, Next.js when it belongs on the web, with Firebase or a REST backend depending on what the data actually needs.
What you get
- Working iOS and Android build from a fixed scope
- Authentication, data layer, and admin surface
- Store submission assets and release walkthrough
- Source, documented, in your organisation's repository
Fixed quote after a scoping call
- S-021–3 weeks
AI feature integration
A model dropped into a product you already run: classification, extraction from documents, or an assistant that answers from your own records instead of guessing.
What you get
- Evaluation of whether a model is the right answer at all
- Working feature behind an API you control
- Prompt and pipeline documentation your team can edit
- Cost and latency figures measured, not estimated
Fixed quote, or a paid two-day evaluation first
- S-034–10 weeks
Institution operations system
The CampusNova problem, applied to your organisation: attendance, billing, records, and the enquiries that currently arrive by phone. Schools, hostels, clinics, academies.
What you get
- Attendance and records, biometric or manual
- Automated billing reminders on your schedule
- Staff dashboard and role-based access
- Training session for the people who will run it daily
Milestone-based, quoted per module
- S-041 day to 6 weeks
Teaching and workshops
Cohort teaching with a shipped artefact at the end. Either Flutter and Firebase from empty repository to working product, or AI fluency for a team that keeps using models badly.
What you get
- Session plan agreed before we start
- Live build, not slides — everyone ends with running code
- Exercises and reference material to keep
- Follow-up session two weeks later
Per cohort
How a freelance engagement runs
- 01
Scoping call
Thirty minutes. I ask what breaks today and who is paying for it in hours. If software is not the answer I will say so on the call.
- 02
Fixed quote
A written scope with milestones and a price, not an hourly estimate that drifts. You approve it before anything is built.
- 03
Weekly drops
Something running every week, in your hands, not a demo at the end. Scope changes are re-quoted rather than absorbed silently.
- 04
Handover
Source in your repository, documentation written for whoever inherits it, and a session with the people who will run it.
- 05
Two weeks after
Post-launch support included. Real usage finds things testing does not, and that period is when it happens.
What I decline
- Open-ended maintenance retainers with no defined scope
- Design-only work — I build what I design
- Projects where the deadline is already impossible and everyone knows it
- Anything that needs the data to be described as more real than it is
Saying no to four things is how the other work gets delivered on the date I gave you.
Tell me what breaks today.
Include what the manual process currently costs you in hours, who is paying that cost, and the date it needs to stop. That is enough for me to come back with a scope and a number.