Freelance PHP developer in South Africa.

The business problem

Businesses need to buy and distribute airtime, data, SMS and prepaid electricity through repeatable workflows. Supplier processing can be delayed, so accepting an order and confirming delivery need to be handled as separate steps.

My work

I develop customer and admin tools, API integrations, bulk and recurring order workflows, and the background processing that follows orders through to their outcome. The work includes wallet and transaction reporting, plus OAuth-based MCP access for supported AI tools.

A key implementation decision

For uncertain electricity orders, recovery queries the original reference before any further action. A delayed response needs reconciliation; repeating the purchase can create a second charge.

Engineering challenges

• Keep queued, submitted and confirmed supplier outcomes distinct across customer screens, workers and reports.
• Carry the original order identity through recovery so a transport failure does not become an automatic second purchase.
• Separate account-scoped reporting access from transaction permissions in OAuth and MCP integrations.

The business problem

A business distributing airtime rewards needs to order voucher PINs, give them to recipients, and track redemption. These are distinct events: creating an order does not mean a recipient has received airtime.

My work

My work covers voucher ordering and distribution, customer and admin workflows, and the API used by business integrations. The API supports balance checks, ordering, order retrieval and voucher-status queries, with documentation explaining the boundaries of each operation.

A key implementation decision

Keep ordering, distribution and redemption status distinct throughout the workflow. A submitted redemption still needs its supplier outcome checked, and an uncertain response must be investigated before it is repeated.

The business problem

A voucher sale is only the start of the service. Customers need to register pets and activate benefits; staff need to review claims and manage aftercare. Payments, customer records and service history need to remain connected.

My work

I developed purchase and voucher workflows, pet registration and activation, customer accounts, and role-based staff tools. Supporting work includes payment verification, wallet and order records, certificates, queued notifications, and wholesale and corporate workflows.

A key implementation decision

Verified payment issues the voucher; pet registration and explicit activation establish the benefit. Keeping these steps separate makes the customer journey clear and gives staff a record of the applicable dates and terms.

Engineering challenges

• Reconcile verified funding against the original order amount before issuing voucher units.
• Use transactions, row locks and replay checks around financial and redemption writes.
• Keep payment, activation, claims and aftercare history connected while enforcing customer and staff permissions.

The business problem

A publisher working across podcasts, webinars and industry discussions needs to organise different kinds of content and keep them connected. The team also needs a practical way to publish and maintain that material.

My work

I built the PHP/MySQL platform, including podcast episodes and clips, webinar listings, industry leader profiles, series, municipal briefs, and subscriber and enquiry flows. The admin area gives the team dedicated screens to manage those content types.

A key implementation decision

Give each content type an appropriate editing workflow. Municipal briefs, for example, have editing and preview tools so the team can review the presentation before publishing.

The business problem

A practice website needs to explain the services, answer common questions, and make booking or getting in touch straightforward, particularly for someone visiting on a phone.

My work

I built the responsive website with dedicated service pages, practice information, pricing guidance and FAQs. Booking, WhatsApp, telephone and directions links provide clear next steps. Technical SEO work includes page metadata, canonical URLs, structured data and a sitemap.

A key implementation decision

Keep the site simple to operate with shared PHP content and layouts. Track enquiry actions such as booking and WhatsApp clicks separately from page views, so reporting can distinguish the actions visitors take.

The business problem

A useful business directory needs consistent records, a way to check where information came from, and a process for owners to manage their details. Supporting different countries also introduces differences in addresses, phone numbers and locations.

My work

I built the directory and its administration, owner workspaces with CRM and enquiry tools, and REST/OAuth/MCP publishing routes. Supporting data workflows collect and review listing evidence, retain source information, and organise businesses by service and place.

A key implementation decision

Preserve the source and review history behind published details. Keep public business profiles separate from private owner records, with explicit permissions for team and agency access.

The curation engineering

The surrounding harness coordinates source collection, bounded AI writer tasks, stale-output detection, completion accounting and controlled publication. A Go service handles concurrent source retrieval; PHP owns the curation workflow and validation. Explore the harness and its recovery controls.

The business problem

A business offering services and selling equipment needs to accommodate two customer journeys: understanding a service and making an enquiry, or finding a product and placing an order.

My work

I developed the public service pages and PHP/MySQL storefront, with product details, a cart, checkout and customer accounts. Administration tools support product, order and customer management.

A key implementation decision

Give service enquiries and product purchases their own routes through the site. Keep customer order history connected to the account, and provide staff with the corresponding order-management screens.

The business problem

People considering a specialist service need to understand what the business offers and how to make contact. The website needs to explain the services clearly enough to support that first conversation.

My work

I built the website around the agency’s services, including private investigation, surveillance, tracking and background checks. The site combines service information with telephone, email and enquiry-form contact routes.

A key implementation decision

Place contact options alongside service explanations so visitors can get in touch while reading about the work relevant to them.

The product idea

Give people the experience of browsing, filling a trolley and waiting for a delivery, followed by a reveal of what they did not spend. The purchases, wallet funds and deliveries are simulated; no real payment or delivery takes place.

My work

I developed the SvelteKit progressive web app and procedural PHP/MySQL API, covering account verification, the catalogue, persistent trolley state, a simulated wallet, map-based delivery animation and the server-timed reveal. The application also includes referrals, product administration and funnel reporting.

Engineering challenges

• Keep the interface, API and stored trolley state consistent across navigation and returning sessions.
• Record simulated wallet amounts in integer cents, with ledger entries and duplicate protection for rewards.
• Combine an installable app shell and cached assets with authenticated, server-owned account and checkout state.

The product problem

Drawing a line on a map is not enough to create a useful running loop. The application needs to find routes near a requested distance, check that they return close to the start, compare repeated paths, and explain when the routing engine cannot produce an acceptable result.

My work

I built the SvelteKit map interface and procedural PHP API for accounts, geocoding, route generation, saved routes and exports. MapLibre renders the map, TileServer GL serves vector tiles, and Valhalla supplies route geometry and maneuver instructions. MariaDB stores account and route records.

Engineering challenges

• Evaluate candidate routes against distance and loop-closure checks, then rank options using distance and repeated-path penalties.
• Distinguish map coverage from available routing data and return a clear failure when no acceptable loop is found.
• Count successful route generations against quota while leaving failed attempts and GPX exports outside that count.

The business problem

Customers choosing stone, pebbles, gravel and paving need to see the products, understand their uses, and discuss quantities and delivery. A catalogue needs to support those decisions before an enquiry reaches the business.

My work

I developed the website with product ranges, photographs, landscaping examples and dedicated product and paving pages. How-to content explains possible applications, while telephone, email and contact-form routes connect interested customers with the supplier.

A key implementation decision

Use product images and practical descriptions to support a quote-led sales process. The site gives customers information to start the conversation, with order quantities and delivery requirements discussed directly with the business.