Business websites
Sites built around what the business actually does, not a template with a logo dropped into it. WordPress when a team needs to edit content themselves; static when speed and security come first.
05 · Client web studio
We build for clients what we already built for ourselves.
Websites, publications, and web applications — designed and shipped to the same standard as the eight properties Devsoll runs in-house.
- Properties shipped
- 8
- Articles published
- 603
- Accessibility score
- 100
- Verticals with live proof
- 6
Overview
Devsoll Studio
Devsoll Studio is the client-facing arm of the company, and it exists for an unusual reason: everything we offer here, we built for ourselves first. Six consumer publications, a serverless AI application, and this company’s own website were all designed, built, and are still operated in-house.
That changes what a portfolio means. Ours is not a set of commissions we can only describe — it is a portfolio we own, run, and can show you working today. The same pipelines that let us publish 603 articles across six properties are the systems client work runs on, which is why we deliver in days what is usually quoted in months.
At a glance
Division05
FocusClient web design and build
PlatformsWordPress and static
Properties shipped8
Accessibility score100
EngagementFixed scope
Capabilities
What this division actually does.
Concrete functions we run in-house — not a service menu we would assemble if asked.
Content publications
Complete editorial properties: category architecture, researched articles, structured data, author systems, and the legal pages a monetisable site is required to carry.
Web applications
Static-first applications on edge infrastructure, with pages generated from structured data rather than hand-authored. Our own runs 117 interactive tools on serverless compute.
Technical SEO
Structured data, metadata, internal linking and crawl hygiene handled at build time. Across our own network we corrected 1,018 missing image descriptions and rewrote 157 meta descriptions.
Performance and accessibility
Core Web Vitals and WCAG AA contrast treated as build requirements rather than post-launch cleanup. Every property we operate scores 100 for accessibility.
Migration and deployment
Host migrations, nameserver moves, apex redirects and DNS cutovers, executed without downtime and without losing existing search rankings.
Proof
Built by this division, still operated by it.
Every property below is live and public. Visit any of them — that is the point of listing them.
-
Café ordering agent
Live demoA working WhatsApp-style ordering agent you can talk to. It answers menu and delivery questions, takes an order, and prices it in code rather than trusting the model with arithmetic.
-
Finch & Fortune
LiveA personal-finance publication of 117 articles, built to the heightened trust standards Google applies to financial content.
-
The Nourish Kitchen
LiveA recipe publication carrying full Recipe structured data — the requirement for appearing in Google’s rich recipe results.
-
AI Toolbox
LiveA web application serving 117 interactive tools from edge infrastructure, with pages generated programmatically from structured data.
-
The Style Edit
LiveA fashion publication of 114 articles across twelve sections, designed around visual discovery as much as search.
-
Health, beauty and home network
LiveThree further publications — fitness, skincare, and home decor — sharing one technical standard and one editorial discipline.
-
This website
LiveA seventeen-page corporate site organising five divisions under one brand, deployed with a full host and DNS migration.
Our process
Four stages, every project.
Division-specific expertise sits on top of one operating discipline. This is that discipline.
-
Scope before design
Every project begins with a written scope: what is being built, what is not, who provides what, and when. Most failed web projects fail here, in the gap between what was assumed and what was agreed. We close that gap before any design work starts.
-
Concept, then approval
We present a homepage concept before building anything else. Direction is corrected early, when it is cheap, rather than at delivery, when it is not. Nothing further is built until that concept is signed off.
-
Build on the system
Content, structured data, accessibility and performance passes run through the same tooling that operates our own network. That is where the speed comes from — the work is not being improvised for each project.
-
Hand over completely
You receive the site, the logins, a written record of what was built, and instructions for running it. Our access is removed and credentials rotated at handover. You own the property outright — we hold nothing hostage.
Questions
About Devsoll Studio.
WordPress if you or your team will edit content regularly. Static if speed, hosting cost and security matter more than in-house editing. We recommend based on how you actually work, not on which is easier for us to build.
You do, entirely. The domain and hosting stay in your name throughout, and at handover our access is removed and credentials rotated. Nothing about the arrangement depends on you staying with us.
Yes. It is the part most studios leave to the client, and the part most often left unfinished. We use an AI-assisted pipeline we built ourselves, edited before publication — the same system behind the 603 articles across our own network.
No, and we would treat anyone who does with caution. Rankings and ad-network approvals are decided by Google, not by your developer. What we commit to is building to the technical and editorial standards those decisions are actually based on.
Elsewhere in the portfolio
The rest of the company.
Work with us
Start a conversation with Studio.
Tell us what you are trying to build and we will tell you plainly whether we are the right fit.