One job, done well
A single feature that fixes one problem on the site you already have.
- Quote calculator
- Booking form
- PDF report
WordPress & WooCommerce developer
I build tools that solve real problems for real teams
I design the screens your team actually wants to open, then build the engine underneath on the WordPress and WooCommerce you already run. No new platform, no per-seat SaaS bill.
1.1m rows load tested
4 roles, one sign-in
Your Dash
OverviewOrdersBookingsInvoicesTeamReports
OverviewGood morning, team
+ NewOrders today128+12%
RevenueR 48 250+8%
Open tasks14
Bookings23
This week
Needs attention
Quote for Hall & CoSent
INV-0042 overdue2 days
Staff rota for MayDraft
Supplier order #318Approved
Built on the tech your business already runs
WordPress
WooCommerce
Elementor
REST API
PWA
1.1mrows in the MasterDash load test
98 msdashboard load with 25,000 records
4 roleson the training platform, owner to learner
0WordPress logos your clients ever see
How it fits together
Tools plug into dashboards. Dashboards grow into platforms.
Everything I build starts as a small tool that does one job well. Tools plug into a dashboard, and dashboards plug together into a platform you own.
Tools working together
One screen for one team, with roles, tasks, numbers and sign-offs in one place.
- Client portal
- Ops dashboard
- Team tasks
Dashboards for every team
Sign-in, payments, roles, white label and your own rules, on software you own.
- Training platform
- Practice management
- Marketplace
Why it matters
I build what the problem needs. Nothing more.
Not every team needs a platform
If one task is slowing you down, a single tool fixes it quickly and for a fraction of the cost. It plugs into a dashboard later if you grow.
Some owners need full control
Your own sign-in, payments, roles and brand, with no per-seat SaaS bill and nobody else's roadmap. That is a platform you own outright.
Selected work
Three teams, three problems, one way of building
Each project started with a team doing important work in the wrong tool. Every case study shows the design and the engine side by side.
Client portal · WP plugin
Read the case study
MasterDash
One dashboard for an HR, OD and L&D practice, with a private portal for every client.
DesignFive role-based dashboards and guided client onboarding
EngineCustom tables and a locked-down REST API
Training platform · WP plugin + PWA
Read the case study
McMaster Training Platform
The engine behind McMaster Training. Documents become packs and pathways, sell through WooCommerce and run in the room from a phone.
DesignA4 documents in the house style and a trainer mode for phone and tablet
EnginePayfast checkout, team plans and white label
Website · Redesign
Read the case study
McMaster Training website
The shop window for 12 training pathways, redesigned so facilitators see exactly what they download.
DesignA document wall hero and bold pack cards
EngineHand-built Elementor sections on WooCommerce
How I work
Every build has two halves. I do both.
When one person designs the screens and another builds the database, something gets lost in between. I design the screen and write the code that feeds it, so the two always agree.
The design: what your team sees
Every screen is prototyped first on sample data, so you click through the real thing and sign it off before a line of the engine is written.
Clickable prototypeTest it first
Built per roleOwner to learner
Phone firstFor the floor
Your brandNot WordPress
ink
deep pink
white
paper
AaMontserrat 400 to 800
One type family, strict scale
One type family, strict scale
The engine: what runs it
The approved prototype compiles into a proper WordPress plugin with real data, real roles and tests on every release.
- Own indexed tables that stay fast at hundreds of thousands of records
- Rules on the server. Clients only ever receive their own data
- Installable apps with PIN sign-in that keep working offline
- WooCommerce underneath for anything that sells or downloads
// every client request is checked on the server register_rest_route('masterdash/v1', 'ws/inv/(?P<id>\d+)', [ 'methods' => 'GET', 'callback' => [MD_Invoices::class, 'get'], 'permission_callback' => [MD_Auth::class, 'can_read'], ]);
ScreensCompiled from the prototype
API + rulesREST routes, roles, PINs
BaseYour WordPress site
What I build
Engines on top of tech you already own
If your business runs on WordPress or WooCommerce, you already have users, payments and hosting. I build the part that is missing.
- Ops dashboardsDaily numbers, tasks and sign-offs for busy teams→
- Client portalsClients sign, submit, approve and pay→
- WooCommerce enginesSubscriptions, downloads and custom checkouts→
- Installable appsPWAs with PIN sign-in and offline mode→
- Reports and PDFsP&L, invoices and survey reports→
- Help built inIn-app guides and a manual per role→
The process
From the problem to a working app
You see your tool working before you pay anything.
-
1
Connect with me
Tap the button and say hello on WhatsApp.
WhatsApp me -
2
Fill in a quick form
Tell me what you want to solve, in a few short questions.
-
3
Get a working prototype
I send you a clickable prototype on sample data. No payment, no risk.
-
4
Sign off and I build
Happy with it? I build the real thing: a tool, a dashboard or a full platform.
-
5
You launch
It goes live on your site, with help screens and a manual for each role.
Collaborations
Got a cool idea but no budget to develop it?
I work with a select few creative entrepreneurs to help turn their ideas into reality. Not every tool makes the cut. A few simple questions help me decide whether the technology you want to launch is viable, and whether I'd be a good fit.
- Click startThe application opens right here on the page.
- Add your details and sign the mutual NDAIt protects your idea, and the free sample prototypes I share with you, if we decide not to work together in the end.
- Answer three questionsWith space to add anything else I should know.
- Hear back from meExpect an answer within a few hours.
Collaboration application
Tell me about your idea
Your details, a mutual NDA, then three short questions. Your idea stays protected from the first step.
- Mutual NDA before you share anything
- Three short questions
- Free sample prototypes if it's a fit
Thank you, there.
Your application is in and your NDA is signed. Steph will be in touch shortly.
Reference
Signed
Download signed NDA (PDF)
A copy is on its way to your inbox.
This agreement is between Stephenie Venter (steph.co.za, hello@steph.co.za) ("Steph") and the person named in the signature section, together with any business or project they name ("the Applicant"). Each is a "Party". It is mutual: it protects what each Party shares with the other.
1. Purpose
1.1 The Applicant wants to share an idea for a product, tool, dashboard or platform with Steph so that the Parties can decide whether to work together on it. Steph may share sample prototypes, designs, code and working methods with the Applicant as part of that conversation. This is "the Purpose".
2. Confidential Information
2.1 Confidential Information is any information one Party ("the Discloser") shares with the other ("the Recipient") for the Purpose, in any form and whether shared before or after this agreement is signed. It includes ideas, concepts, business models, plans, pricing, customer and supplier information, data, designs, wireframes, prototypes, source code, technical methods, and the fact and content of the Parties' discussions.
2.2 Sample prototypes, designs and code that Steph shares are Steph's Confidential Information.
3. What is not confidential
3.1 Information is not Confidential Information if the Recipient can show that it: (a) is or becomes public other than through a breach of this agreement; (b) was already lawfully known to the Recipient, without restriction, before it was shared; (c) is lawfully received from someone else who is free to share it; or (d) is developed independently by the Recipient without using the Discloser's Confidential Information.
4. What each Party promises
4.1 To use the other Party's Confidential Information only for the Purpose.
4.2 To keep it confidential and protect it with at least the care it uses for its own confidential information, and never less than reasonable care.
4.3 Not to disclose it to anyone except its own employees, contractors or professional advisers who need it for the Purpose and are bound by confidentiality duties at least as strict as these. The Recipient is responsible for anyone it shares with.
4.4 Not to copy, reverse engineer or decompile any prototype, design or code, except as needed for the Purpose.
4.5 To tell the Discloser promptly if it becomes aware of any unauthorised use or disclosure.
5. Disclosure required by law
5.1 If the law, a court or a regulator requires the Recipient to disclose Confidential Information, the Recipient may disclose only what is required. Where it is lawful to do so, the Recipient will first give the Discloser notice so that the Discloser can seek protection.
6. Ownership of ideas and work
6.1 Confidential Information remains the property of the Discloser. This agreement grants no licence or other right in it, except the right to use it for the Purpose.
6.2 Steph will not build, sell or share the Applicant's idea, or help anyone else to do so, without the Applicant's written agreement.
6.3 This agreement does not stop Steph from using her general skills, know-how and experience, or from building tools, dashboards and platforms for other clients, provided she does not use the Applicant's Confidential Information. Steph's pre-existing tools, code, templates and methods remain hers.
6.4 Sample prototypes remain Steph's property until the Parties agree otherwise in writing. The Applicant may not use them commercially or give them to anyone else.
7. No obligation to go ahead
7.1 Neither Party has to enter into any further agreement. Any collaboration, build or payment will be covered by a separate written agreement.
7.2 Confidential Information is shared as it is, without any warranty.
8. Returning or deleting information
8.1 If the Discloser asks in writing, or if the Parties decide not to work together, the Recipient will return or delete the Discloser's Confidential Information within 14 days and confirm this by email. Copies that the law requires the Recipient to keep, or that sit in routine automatic backups, may be kept but remain confidential.
9. How long it lasts
9.1 This agreement starts on the signature date. The confidentiality duties last for three years after the last date on which Confidential Information is shared, and for trade secrets and source code for as long as they remain secret.
10. Remedies
10.1 A breach of this agreement may cause harm that money alone cannot fix. The Discloser may apply for an urgent interdict or other relief, in addition to any other remedy it has.
11. Personal information
11.1 Each Party will treat personal information it receives under this agreement in line with the Protection of Personal Information Act 4 of 2013 (POPIA).
11.2 The Applicant agrees that Steph may keep the details submitted with this agreement (name, contact details, signature, answers, submission time and IP address) to administer this agreement and the application.
12. Electronic signature
12.1 The Parties agree to conclude this agreement electronically, as allowed by the Electronic Communications and Transactions Act 25 of 2002. The Applicant's drawn signature, together with the date and time stamp and the record of the submission, is the Applicant's signature.
12.2 Steph accepts this agreement electronically at the moment the Applicant's signed copy is recorded. A copy is then emailed to both Parties.
13. General
13.1 This is the whole agreement between the Parties about its subject. Changes are only valid if made in writing and agreed by both Parties.
13.2 A delay in enforcing a right is not a waiver of it. If any part of this agreement is invalid, the rest stays in force.
13.3 Neither Party may transfer its rights or duties under this agreement without the other Party's written consent.
13.4 Notices may be sent by email to the addresses in this agreement.
13.5 This agreement is governed by the law of South Africa. The Parties consent to the jurisdiction of the High Court of South Africa, Gauteng Division, Johannesburg.
Version 1.0, 3 October 2026
Questions
Before you message me
Do I need to move off WordPress?
No. That is the point. I build on the WordPress or WooCommerce site you already have, or set up a fresh install for the app on its own subdomain.
Who owns the code?
You do. You get a normal WordPress plugin installed on your hosting. There is no per-user licence and nothing stops working if we stop working together.
How long does a dashboard take?
A focused tool with a few roles usually takes weeks, not months. You see a clickable prototype early, so you know exactly what you are getting before the build starts.
How do you quote?
I quote each phase as a range of hours at a fixed rate, so you see the lowest and highest cost up front and pay for milestones as they are delivered.
Can you work on a site someone else built?
Yes. Most of my work sits on top of existing sites. I check what is there first and tell you plainly what should stay and what should go.
Got a spreadsheet your team hates?
Send me a WhatsApp with what your team does every day and where it breaks. I'll tell you honestly whether a dashboard fixes it, and what it would take.
WhatsApp me now
Opens a WhatsApp chat with Steph