24 September 2026 / 6 min read
What a Lovable Expert certification actually means
Rees Cowne is a certified Lovable Expert App & Web Builder. Here is what that covers, where it fits alongside custom code and WordPress, and why it does not mean everything is built by AI.
- certifications
- process
- custom build
Rees Cowne recently passed the Lovable Expert App & Web Builder certification. This is a short, honest note about what that means, where it fits, and what it does not change about how outhang works.
What the certification actually is
Lovable Expert is a practical certification, not a badge you collect by attending a webinar. It is assessed against building real apps and real websites on the platform, to a standard a reviewer signs off on.
The areas covered are the ones that matter when something has to ship and stay shipped:
| Area | What is assessed |
|---|---|
| App architecture | Data modelling, auth, permissions, the structure that lets a product grow without a rewrite |
| Web build quality | Layout, responsiveness, accessibility, performance — the things a client sees and feels |
| Data and security | Row-level security, safe client access, secrets handling, not leaking data between users |
| Deployment and ownership | Shipping, versioning, handover — owning what was built, not renting it |
It is a bar, not a crown. Passing it means the work meets a standard a third party checked.
Where it fits in the toolkit
outhang does not build everything on one platform. The full explanation is on the credentials page, but the short version: we choose per brief between fully custom code, WordPress done properly, bespoke databases and internal systems, and modern build platforms.
Lovable is one of those routes. It is the right answer for some projects and the wrong one for others. A content-led site a marketing team needs to publish on themselves is still usually WordPress. A system with unusual business logic or a very long lifespan is still usually custom code. Where the fit is right — and only where it is right — a modern build platform compresses what would be months of work into days or weeks, with the same review, testing and security standards applied.
The certification means we can use that route properly. It does not mean we use it for everything.
"So you just use AI?"
This is the question worth answering directly. The certification does not mean a tool builds things and we watch.
What it means is the opposite. The judgement, architecture, data modelling, security review and ownership stay here. The platform compresses the time between a decision and a working build, for the projects where that is the right route. Strategy does not move. Design judgement does not move. Engineering and security do not move.
A useful way to think about it: the certification is evidence that the operator knows where the guard rails are. The tool does not decide where they go.
What changes for clients
For projects where the platform is the right fit: faster delivery, earlier working prototypes, and the same standards applied as fully custom work. For projects where it is not: nothing changes. We still write custom code, still build WordPress properly, still model databases by hand.
There is no lock-in. If a product outgrows the platform, we migrate it to custom code and own the result. If a brief is better served by WordPress, we build WordPress. The brief builder routes each project to the route that suits it, with three priced tiers.
Certified to build faster, experienced enough to know when not to
That is the line. The certification is one capability among several, used when it is the right one. You can see the background and credentials page for the full track record, or look at the work we have shipped across custom code, WordPress, databases and platforms. If you have a project in mind, the quickest route to a real answer is the brief or a meeting.