Client portal
Project status, file exchange, messaging and invoices. Access control is enforced server-side, so your data is not visible to other clients.
How we work
A process is only meaningful if it produces artefacts you can point at. Every stage below names its output, so at any moment you can check whether it actually happened rather than take our word for it.
Delivery process
The same sequence on every engagement, scaled to the size of the work. A two-week website runs through all seven; it just spends less time in each.
We learn how the business actually works — the process, the constraints, the systems already in place, and what has been tried before. Mostly listening and asking awkward questions.
Scope, sequence and trade-offs get decided and written down: what is in, what is deliberately out, what it costs and roughly how long it takes.
For interfaces, the layouts and states. For systems, the data model, API contracts and integration points. Either way, the structure is agreed before code gets expensive to change.
Built in vertical slices so each milestone is working software you can use, not a percentage. You see progress in the client portal and in demos, not in status reports.
Automated tests for behaviour, manual passes for the things tests miss, plus accessibility, responsive and performance checks. For AI work, a graded evaluation run.
Deployment, environment configuration, redirects where URLs change, monitoring switched on, and a post-launch verification pass before anyone declares it done.
A handover session with your team, documentation they can act on, and an agreed support arrangement — so the system stays maintainable with or without us.
Engagement terms
The commercial side, stated plainly. The full terms are in our Terms of Service; this is the summary that matters day to day.
Working together
You get a client portal account at kickoff. Project status, files, messages and invoices all live in one place, and the people replying are the people building.
Project status, file exchange, messaging and invoices. Access control is enforced server-side, so your data is not visible to other clients.
Book a slot directly rather than going through a form queue. The first call is a scoping conversation, not a sales pitch.
Invoices are issued in the portal and paid by card through Stripe. Milestone billing on larger projects keeps payment aligned with delivery.
Questions
Cost, timelines, payment, revisions, ownership and support — answered without the usual hedging.
It depends on scope. A compact website build starts at $499, a full custom backend or web application at $1,499, AI agent work at $799, and prompt engineering at $299. Larger platform work is quoted per engagement. Every service page lists its current tiers, and you get a fixed written quote after discovery rather than a range.
A compact website is typically two to four weeks. A full backend or web application is usually four to ten weeks depending on integrations. Marketing retainers are ongoing and reviewed monthly. We agree the timeline in the strategy stage and tell you immediately if it slips — early, not at the deadline.
Card payments through Stripe, invoiced from your account in the client portal. Larger projects are split across milestones so you are never paying far ahead of delivered work. We never see or store your card details.
Every tier includes a defined number of revision rounds, and those rounds exist to correct our work against the agreed scope. If we have built something that does not match what was signed off, we fix it at our cost. New requirements discovered along the way are quoted as a change rather than absorbed silently — which keeps both the timeline and the invoice honest.
Yes. Every engagement ends with a handover session and documentation, and you can add an ongoing support arrangement with an agreed scope and response expectation. Support is a stated arrangement, not an open-ended promise.
You do, from the start. Repositories, infrastructure, domains and third-party accounts are in your name. There is no Hirelyx layer anything depends on at runtime, and no licence to renew.
Often, and it is frequently the better arrangement. We usually begin with a read-only review that produces a written assessment of the codebase — dependency state, test coverage, correctness risks and the highest-value changes — before anything is agreed.
A named decision-maker who can approve scope, access to the systems involved, and timely feedback at review points. Most delays we see are access delays. We list exactly what is needed in the strategy stage so nothing is discovered late.
Tell us what you are trying to achieve. We will tell you what it takes, what it costs, and whether we are the right team for it.