Applications behind a login
Customer portals, staff tools, dashboards - anywhere people need their own account and their own view of the data.
A brochure site shows people what you do. At some point a business needs the site to do something: take a booking, price a job, hold customer records, talk to the software you already pay for. That is a different kind of work, with different risks, and it is worth knowing which one you are actually buying.
A system is the connections, not the pages
Not a bigger website. Software that happens to live in a browser, with the unglamorous parts that decide whether it is still working in two years.
Customer portals, staff tools, dashboards - anywhere people need their own account and their own view of the data.
Your site, your accounting, your stock, your payment provider. Most of the value is in the connections, and most of the cost is in the edge cases.
A database designed for the questions you will ask of it later, not just for the form that fills it today.
Backups, error alerts, access control and a way to roll back. Boring until the first incident, decisive after it.
If you already know the shape of what you need, the specifics have their own pages: booking systems, progressive web apps, automation and scripts and analytics and tracking. If the job is mainly how the site looks and reads, that is web design.
Custom software is the most expensive way to solve a problem that an existing tool already solves. We will say so before quoting, not after.
If a product you can subscribe to covers 90% of the need, the right advice is to subscribe and spend the difference on marketing.
Building software around a workflow nobody has agreed on means paying twice: once to build it, once to change it.
Every system needs someone whose job includes it. Without that, it drifts out of date and quietly stops being used.
Sometimes the answer is a script between two tools you already have, not a new application around them.
Not mock-ups. Four live sites, and the write-ups behind three of them.
The things people ask before they commit to anything.
It follows the number of distinct things the system has to do and how many places it connects to, not the number of pages. We scope it in writing first, and if the honest answer is that an existing product is cheaper, you will hear that instead of a quote.
Longer than a website and in stages. We aim to get a usable first version in front of real users early, because that is when the requirements that nobody mentioned appear.
Yes. Code, database and hosting in your name, with the handover documented. You can take it to another developer without asking us.
That is a fair question to ask anyone small. We build on ordinary, widely known technology rather than anything exotic, and hand over documentation, so another developer can pick it up without a translation layer.
Often. We read it first and tell you honestly whether it is worth continuing or worth replacing - and that answer is sometimes expensive to hear, which is why it comes before any work starts.
Tell us what you need and what it is for. You get a written scope and a fixed price before anything starts. Email info@webcodexcyprus.com, call +357 94 119060, or use the quote form.