SITE DEVELOPMENT
CUSTOM BUILD
- from 2 weeks
- full cycle
A project that fits no template: its own logic, an architecture built for the case, integrations with outside services. We price work like this separately — from mapping the process to launch and support.
WHO IS IT FOR?
Three situations where no off-the-shelf solution exists
- .01
NO SUCH PRODUCT EXISTS YET
You are launching a service, a platform or a marketplace — something the market does not sell ready-made. Every contractor you talk to starts by asking what to build it on, then offers to stretch the job over whatever platform they already know. The costlier part is elsewhere: until the idea is described as a system, it can be neither priced nor built. The project stalls not for the want of developers but for the want of an architecture.
- .02
STITCHED TOGETHER AND COMING APART
The site on one platform, the accounting on another, payments through a third, and part of the data in spreadsheets. Every join is held together by exports, manual reconciliation and one person who knows where everything lives. Something quietly swaps places: the team stops working for the business and starts working to keep the construction standing. Any change runs into the fact that you cannot touch the system in one place without breaking it in two others.
- .03
THE JOB EXISTS, THE NAME FOR IT DOES NOT
It is not a store, not a corporate site and not a CRM — it is something of its own: a booking service, an exchange, a platform for a community, a tool for one industry. No category on any studio’s website fits it. The problem is almost never the technology. It is that the job first has to be broken down into processes, roles and data — and only then does it become clear what to build, and in what order.
WHAT'S INCLUDED
We do not build below this line
- - Discovery and architecture.01
- - Custom design, never a template.02
- - Responsive on every device.03
- - Built from scratch, no off-the-shelf assemblies.04
- - Roles and access rights.05
- - Integrations with third-party services.06
- - Admin panel by LUNO.07
- - Launch on our servers.08
- - Documentation and project handover.09
- THIS IS THE FLOOR, NOT A PACKAGE
Everything listed ships in every project — even the simplest and cheapest one. There are no stripped-down versions.
- WE START WITH DISCOVERY, NOT WITH MOCKUPS
Until the job is broken down into processes, roles and data, any estimate is a fiction. Discovery is the first stage of the work, and what it produces stays with you either way.
- THERE IS NO CEILING
We do not assemble from templates, so we never run into someone else’s limits. From there the system is built out around how your process actually works: load, integrations, roles, external services.
Keep it short and to the point
WHAT'S INSIDE
EVERY SITE GETS ITS OWN DESIGN
We do not take ready-made assemblies and we do not bend a business to fit somebody else’s grid. The design is built around the job: structure, typography, states, motion. Which is why no two of our projects look alike — compare them yourself.
THE LUNO ADMIN PANEL
Products, copy, prices, pages, banners — all edited from the panel. Plus sales and traffic figures, roles for staff, a log of who changed what. You do not need us for the everyday work, only for what genuinely takes development.
SPEED, AND BEING FOUND IN SEARCH
The site is built on a modern stack with server rendering: pages open fast, search engines see the full content, and the Core Web Vitals sit in the green. Heading structure, structured data and readable URLs go in from the start, not “later, when we get round to SEO”.
LAUNCH AND LIFE ON OUR SERVERS
The project moves onto infrastructure configured for it: monitoring, backups, updates. The infrastructure is run by someone with twenty years behind them. Seven clients in ten stay with us after launch — it usually works out cheaper than finding a contractor every time something small comes up.
CATEGORIES
Three levels of scope. Yours is the one you recognise yourself in
DISCOVERY AND ARCHITECTURE
WHEN IS THIS YOUR CASE?
The idea is there, but nobody knows its size — not you, and not the contractors you have spoken to. We break the job down into processes, roles and data, describe how the system has to work, and put it into a document: the scheme, the stages, an estimate of time and budget, what gets built first and what can wait. The result is yours whether or not we carry on. If we do, the cost of discovery goes towards the project.
FIRST VERSION
WHEN IS THIS YOUR CASE?
It is clear what to build, and what you need is for it to run and start earning — not for everything to be finished at once. We build the core of the system: the main scenario end to end, roles and permissions, the integrations it cannot go without, the admin panel, launch on our servers. The rest is designed into the architecture but not developed — so you can test the product on real users before you commit the whole budget.
FULL SYSTEM
WHEN IS THIS YOUR CASE?
The product has to stand up to real use from day one: several types of user with interfaces of their own, data exchange with external systems, heavy load, resilience requirements. A full architecture built for growth, split into services where that is justified, monitoring and redundancy, documentation and handover to your team. The logic is designed around your processes rather than bent to fit someone else’s limits.
FAQ
Answers to the most popular questions
The honest answer: before discovery, nobody knows. The range across projects of this type runs from $5.000 for a first working version to $20.000 and up for a full system. That is exactly why the first step is discovery at $1.500–3.000, after which you get the scheme of the system, the stages and an estimate rather than a guessed bracket. If you decide not to continue, the document is yours and you can take it to any contractor.
Discovery and architecture, 1–3 weeks. A first working version, 2–6 weeks. A full system, from 4 weeks. For scale: a marketplace with its own CRM, five payment providers, a referral mechanic and a ticket system took us 40 days. We name the deadline after discovery and hold to it — before discovery any figure is a fiction.
No, it is the usual situation — and the first step exists precisely for it. A specification is not something you are supposed to bring; it is what discovery produces. What we need from you is the substance: how the business works, who the users are, what has to happen, and what must never happen. The rest is our job.
A simple test: if you can describe the job as “a store, but with…” or “a site, only it also needs…”, and one or two things follow the “but”, then a standard service with add-ons is what you need, and it costs less. If five things follow the “but” and they change the logic of how it works, that is a different project. We say so plainly on the first call: selling you expensive development where a store would do is a bad deal for us too.
It will, and on projects of this type that is normal; pretending otherwise is not. So the work runs in stages, each with its own scope and its own price, and the plan can be reassembled between them. If a change turns up inside a stage, we tell you what it means for the schedule and the budget before we start on it. The “we have already built it, you owe us extra” situation does not arise.
Practically anything with an API: payment providers, delivery services, accounting systems, CRMs, messengers, external databases. If there is no API but there are exports, we work with those. If a service has neither, we say so during discovery rather than halfway through development.
The team is assembled around the job: developers, a designer, DevOps, a project manager. The infrastructure is run by someone with twenty years behind them. The architecture is designed by one person who holds it from discovery through to launch — on non-standard work that matters more than the size of the team.
You do. The sources, the rights and the documentation are handed over with the project — this is not a builder, not a subscription and not a tie to us. If you ever decide to change contractor or build your own team, the project leaves with you: we write it so another developer can pick it up.
The project can stay on our infrastructure: monitoring, backups, updates, and development as it grows. With non-standard systems that is the rule rather than the exception — the product keeps changing after launch. How we work after handover is agreed separately: one-off changes, or continuous development with a team assigned to you.