A business website
Five to ten pages that explain what you do and make the enquiry obvious. Fast, mobile-first, findable in search, and editable by you afterwards. Usually two to four weeks.
From a fast company website that turns visitors into enquiries, to a full platform with a customer portal and an admin dashboard behind it. Built on your hosting, in your accounts, with the code handed over at the end.
Five to ten pages that explain what you do and make the enquiry obvious. Fast, mobile-first, findable in search, and editable by you afterwards. Usually two to four weeks.
Your customers sign in and see their own records: orders, cases, documents, status. Removes the daily 'where is my …?' phone call. Usually four to eight weeks.
The system your team actually works in — roles and permissions, workflows, reporting, integrations. This is what replaces the spreadsheet. Usually eight to twelve weeks.
For content-led sites we build a statically rendered site: the pages are generated ahead of time so they load immediately, cost almost nothing to host, and have no database to attack. This website is one of them.
For platforms we use a Node.js API with PostgreSQL behind it, role-based access with JWT, and file storage on AWS S3. Deployment is Docker and Nginx, or a managed platform where that is simpler. Xera Lab, in our portfolio, is exactly this shape: a customer portal and an admin dashboard on one shared API.
Search and speed are part of the build rather than a later pass: real page titles, structured data, correct headings, images sized to what they render at, and Core Web Vitals checked before launch.
A fixed quote in USD after a free scope call. The main driver is not page count but how many user roles the system has and how much of your business logic it has to encode.
A brochure site and a multi-role platform are different orders of magnitude, so the scope call exists to tell you which one you actually need — sometimes it is the cheaper one.
Dental case management platform
Read the case study →
NFC digital business card
Yes. For a content-led site we either wire up a content editor or hand over a simple structure you can change directly, and we show you how. For a platform, content and users are managed in the admin dashboard we build for you.
The technical side, yes, and it is part of the build rather than an add-on: page titles and descriptions, heading structure, structured data, sitemaps, hreflang for multilingual sites, image sizing and Core Web Vitals. Ongoing content and link building is a different discipline and we will say so rather than pretend otherwise.
Yes, including full right-to-left layout, Arabic typography and per-language URLs and metadata. This website runs in five languages with a true right-to-left Arabic version.
You do, directly, in your own account — so you always see the real cost and never lose access. We set it up, tell you what it will cost per month, and include the estimate in the quote.
Tell us what the business does today and where it breaks. You get a recommendation on scope and a written price in USD.