Choose a service to compare focused engagement options for custom software, graphic design, or WordPress websites. Starting prices reflect the smallest practical scope; a final quote follows a clear brief and agreed deliverables.
Systems designed around real work
Custom Software
From workflow assessment to a production system and ongoing iteration. Best for teams replacing paper, spreadsheets, repeated admin, or disconnected tools with software shaped around their actual operations.
Pricing mode
Work with me directly as a freelancer. My pricing basis is R550 per hour, equivalent to R4 400 per eight-hour day. Fixed project fees are confirmed against an agreed scope. International payments via Wise.
Engagement journey
Assessment → Build → Support
Most engagements follow this sequence. Assessment clarifies what to automate, Build replaces the paper workflow, and Support keeps the system aligned after launch.
01
Workflow Assessment
Discover what to automate before you build.
1–2 calendar weeks · R17 600
↓
02
Custom Software Build
Replace the paper workflow with working software.
3–8 calendar weeks · From R66 000
↓
03
Support & Iteration
Keep the system reliable after launch.
By the day · R4 400
Relative effort
Workflow Assessment
1–2 calendar weeks
Custom Software Build
3–8 calendar weeks
Support & Iteration
By the day
Build carries the most effort because it turns the mapped process into production software. Assessment is short and decision-focused. Support is booked by the day as needs appear.
What a focused build might include
As an illustration, a single request-and-approval workflow could cover intake, required-field validation, role-based review, status tracking, an audit trail, and a team handoff. Actual scope depends on the number of roles, exceptions, integrations, reports, and records to migrate. The 3–8 week range assumes timely access to sample cases and decisions from the people who own the process.
Discovery helps establish what is worth automating before committing to a build. This engagement walks your real paper workflow end to end: who touches what, where time and errors accumulate, and which steps create the most operational drag. You receive a decision-ready view of the process as it actually runs, with a recommendation on what to automate first, what to leave alone, and what a sensible first build should cover.
Timeline - 1–2 calendar weeks
The freelancer fee reflects four delivery days, typically spread over 1–2 calendar weeks. Additional processes are scoped separately.
02
Custom Software Build
From R66 000 / projectFreelancer
Replace the paper workflow with working software.
This is the core engagement: turning a mapped paper process into software your team actually uses. Work covers requirements lock, digital flows, data model and validation, build, and validation against real sample cases - not a mock that collapses on day one. Starting price covers a focused single-workflow system. The 3–8 week timeline is elapsed calendar time, not continuous full-time development. Final pricing scales with complexity: number of roles, approvals, reporting, integrations, data migration, and edge cases. An assessment (or equivalent brief) keeps scope honest and delivery focused.
Timeline - 3–8 calendar weeks
Final project price confirmed after scope lock. Hosting and infrastructure billed separately unless agreed otherwise.
The freelancer starting price reflects approximately 15 delivery days for one tightly scoped workflow.
03
Support & Iteration
R4 400 / 8-hour dayFreelancer
Keep the system reliable after launch.
Software only earns its keep if it stays aligned with how the business actually works. Support days cover bug fixes, small features, process tweaks, and short training refreshers as operations change. You book time in day increments; we prioritise what fits the booked block and queue the rest. This is for teams who need a dependable engineering partner after launch without standing up a full in-house bench - or who want controlled iteration instead of letting the system drift.
Timeline - By the day
Billed in day increments. Unused days do not roll unless agreed.