Every quote, invoice, project, support ticket and client record at Samloryx lives in a system we designed, built and deployed ourselves. Not a stack of subscriptions held together by exports.
You are already looking at part of it. This page is served by it, and the assistant in the corner of your screen writes to it.
A consultancy running on six disconnected SaaS subscriptions has the exact problem it sells the cure for. Client data in one tool, invoices in another, project status in a third, and a person in the middle keeping them in step.
So we built the thing we would build for a client, and pointed it at ourselves first. It keeps us honest: every argument we make about custom systems is one we have already had to live with.
A client record entered once is the same record the invoice, the project and the support ticket all point at. That is the whole argument for building rather than buying.
Leads and lead activity, a pipeline kanban, proposals with follow-up tracking, quotations, invoices with generated PDFs, and revenue reporting.
Leads · Pipeline · Proposals · Finance
Clients, projects and milestones, timesheets, structured onboarding with a readiness score, and project reports that draft themselves from what actually happened.
Clients · Projects · Onboarding · Reports
A support desk with SLA tracking and escalation, website enquiries, a shared inbox, meeting and calendar sync, and WhatsApp messaging.
Support · Inbox · Calendar · WhatsApp
Case studies, insight articles and site content are database records edited in the dashboard. Publishing a new article does not need a developer or a deployment.
Case studies · Articles · Content
Analytics across the pipeline, a public-sector tender monitor with requirement tracking, and a daily digest that emails what needs attention rather than waiting to be asked.
Analytics · Tenders · Daily digest
The site assistant answers visitor questions from a knowledge file we control, and every conversation is logged to the dashboard as a record, not lost in a widget.
Assistant · Conversations · Discovery
Every choice here was made so that someone else could take it over. That is the same standard we build client systems to.
Server-rendered pages for anything that needs to be found by search, a JSON API for the dashboard. Long-term supported, and you can hire for it anywhere.
One relational database, with every schema change applied as a numbered migration. The database can be rebuilt from scratch and arrive in exactly the right shape.
A single-page operations dashboard behind authentication, responsive down to a phone, because the business does not stop when you are away from a desk.
Application, database and reverse proxy as containers, with certificates issued and renewed automatically. Small, cheap and unremarkable to run.
An automated test suite runs on every change and has to pass before anything deploys. Some of those tests exist to enforce editorial and compliance rules, not just code correctness.
A merge to the main branch builds, tests and deploys itself, then smoke-checks the live site. Releases are routine rather than an event.
Most consultancies ask you to take their delivery capability on trust, or on the strength of work you cannot inspect because it sits behind a client's login. This platform is the opposite of that. It is in production, it is under load from a real business, and the public half of it is the site you are reading.
It also sets the standard for what we hand over. Documented, migrated, tested, deployable by someone who is not us. If we would not accept it for our own operations, we do not ship it to yours.
To be clear about what this is: the platform is our internal system, not a product for sale and not a subscription you can sign up for. What we sell is the ability to build one shaped around your business.
Start with a conversation about where your operation actually loses time. That is a better first question than what to build.