On this page
You get hired because someone looked at something you built and thought "I want that for my business." That is why the JobTayo foundation ends its client course by having you publish one — you assemble proof as you learn, not afterwards.
Why the usual portfolio fails
- It lists tools instead of outcomes — "Make.com, n8n, Softr" tells a client nothing
- It shows screenshots with no context — pretty, meaningless
- It has no numbers, no before, no after
- It's written for other builders, not for the business owner making the decision
A four-part case study format
| Section | What goes in it |
|---|---|
| The situation | What the business did before, in plain language, and why it hurt |
| The build | What you made, which tools, and the key design decisions |
| The result | What changed — time saved, errors removed, response time, capacity |
| The honesty note | A limitation, a trade-off, or what you'd improve next |
That last section surprises people. Including a limitation makes the rest of the case study more believable, not less — it signals judgment rather than salesmanship.
No clients yet? Build anyway
The most common blocker is "I have nothing to show." You do, once you stop waiting for permission:
- Automate your own work — your inbox, your invoicing, your reporting. Document it like a client project.
- Build for a real small business you know — a sari-sari store, a clinic, a barangay office, a family business
- Rebuild a public process — take a visible, clunky workflow and show a better version
- The exercise in the client course — a niche, a headline, twenty names, one video, a priced project, and the portfolio published at the end of it
A build for your own business is not a fake project. It's a real system with a real user — you. Present it that way.
Make it watchable
A short screen recording beats a thousand words. Show the trigger, show the system running, show the outcome. Clients rarely read a case study to the end; they will watch a short video of something working. Record one short walkthrough for every build you are proud of, and do it while the work is still fresh in your hands.
Protecting client confidentiality
Ask permission before naming a client — always.
- Anonymise: "a small property agency in Australia" works fine
- Blur or replace real customer data in screenshots and recordings
- Describe the process and the result, not the client's private numbers
Where the portfolio lives
Three places: your own site; a short PDF or link you can paste straight into a proposal; and, in time, the JobTayo talent pool, which opens to people who pass a specialisation assessment. The specialisations are still being built, so that third place is not open yet — we would rather say that than point you at an empty page. Your own site does not need to be elaborate. A single index.html file dragged onto app.netlify.com/drop is live in about ten seconds, and a Softr custom code block does the same job. If a prospect has to ask for examples, you've already lost momentum.
Keep it alive
Add a build regularly. Retire the weakest. A few strong, current case studies beat a long list of outdated ones — and the discipline of refreshing them keeps your skills current as the tools change.