On this page
Automations run in the background. Softr is how the business sees them: a database turned into a portal that a client's team, customers or partners can log into and use. No code required, plenty of judgement required.
Where we stand on this today. Softr is a specialisation that is still being built, so it is not open, not priced and cannot be booked. What the foundation does cover is the tool landscape — which layer Softr sits in, the four questions that decide whether it fits, why we went deep on it, why you should be sceptical of us there, and what Softr is genuinely not good at. Everything below is what portal work involves, and it is worth reading whether you learn it with us later or on your own now.
Why Portals Sell So Well
Small businesses run on spreadsheets that nobody outside the office can safely touch. The moment a client wants their customers, contractors, or field staff to see part of that data, they hit a wall. Buying custom software is expensive. That gap is the Softr opportunity — and it's one of the easiest projects to scope, price, and finish.
Data Modelling Before Design
Start where most beginners don't: the data. A portal is only as good as the structure behind it, so the tables and relationships have to hold up as the business grows — and the classic mistakes are cheaper to spot now than to unpick later.
- One table per real-world thing (client, project, invoice) — not one giant sheet
- Relationships instead of duplicated text fields
- Status fields that drive the interface rather than free-text notes
- Deciding what should never be visible to a portal user, before you build anything
Blocks, Lists, and Detail Pages
- Building list → detail flows that feel natural on both desktop and phone
- Filters and search that match how the client actually looks for things
- Forms that write back to the database with validation
- Charts and summary blocks for the person who only wants the headline number
User Groups and Permissions
This is the part that turns a nice interface into something a business can trust. User groups and conditional filters decide who sees which records, and you test the portal as each role before you hand anything over. Treat a permissions bug as a project failure rather than a small fix, because that is how the client will treat it.
The fastest way to lose a client is a portal where one customer can see another customer's data. Test every role, every time, before you send the link.
Connecting a Portal to Automations
This is where the layers meet. A form in the portal triggers a scenario in Make or n8n; the scenario enriches, classifies or generates something with AI; the result appears back in the portal. Data, interface, automation, AI — the four layers the first foundation course teaches you to see, arranged around a single build.
| Portal type | Who logs in | What the automation does behind it |
|---|---|---|
| Client portal | The client's customers | Status updates, notifications, document generation |
| Ops dashboard | Internal staff | Data cleanup, AI summaries, task routing |
| Applicant / intake portal | Applicants or leads | Screening, scoring, scheduling |
| Partner directory | External partners | Sync from CRM, access control, reporting |
Launch and Handover
- Custom domain, branding, and making it feel like the client's product, not a template
- Onboarding the client's team with a short recorded walkthrough
- A simple maintenance agreement so small changes don't turn into free work
What a Finished Portal Proves
A working, permissioned portal is one of the strongest things you can put in a portfolio, because you can open it live in a sales call instead of describing it. That is the kind of build that moves a conversation from VA work towards specialist work. Build yours on invented data and label it a demo — a real client's portal is never yours to show anyone.
How assessment actually works. The three foundation courses each end in a quiz scored automatically against a fixed answer key: 67% to pass, one sitting, a 60-minute limit, no back button, and unlimited retakes after 24 hours with the questions reshuffled. Best score counts. The specialisations end differently — a live assessment call with a person, ₱1,000 per exam, billed separately from the subscription. None can be booked today, because none of them is open yet. Passing one puts you in the talent pool, and that is the whole claim: not an offer of work, and never a job guarantee.
Where to go next
- Inside the JobTayo Academy curriculum — what the foundation covers and in what order
- Make.com for beginners — what the automation layer does, and where it stops
- Backend security for non-developers
- What the three foundation courses cover