Custom web development for businesses

Almost every company we talk to already has a website. What they don't have is the place where a client downloads an invoice, a sales rep sees only their own accounts, or operations marks an order as shipped without emailing three people. That process lives in inboxes, in a shared spreadsheet and in the memory of whoever has been there longest.

Web development starts by naming that process in one sentence: who opens the screen, what decision they make, what data they must not make up, and which system — the ERP, the CRM, email, a shared drive — has to be updated when they finish. If that sentence can't be said out loud, there is no project yet. There is a wish to refresh the homepage.

Design matters because the person who repeats the task forty times a day won't read a manual. The value is in step four no longer depending on someone remembering it. A beautiful interface that doesn't change that step is a brochure with a login.

The client logs in and sees their invoices, not their neighbor's. The sales rep opens the same file and doesn't see the margin if their role doesn't allow it. Operations marks an order “ready”, and the warehouse, which uses another word for the same moment, sees its own. Those words belong to the business. They don't come from a generic “order status” menu.

When an order fails halfway, the screen says what was saved and which system didn't respond. No endless spinner, no “please try again later” that forces someone to call whoever built it. The error is part of the interface because it is part of Tuesday.

The handover session uses that Tuesday, not demo data. The difficult client, the half-finished order, the role that shouldn't see prices. If that session can't be run with real cases, the portal isn't finished yet, even if the design is.

Client portals, private areas, operations tools and products with accounts, roles and states belong here. An order can be placed, ready, flagged or closed. The interface uses those exact words, and permissions decide who can move it from one to the next.

We turn down the pretty prototype that “someone will build later”. Design and implementation sit with the same team because every screen is a decision about data. If the prototype promises a button the system behind it can't deliver, the button isn't drawn and the scope says so.

We also don't force a two-gigabyte drawing, the loading-dock scale or a signature in a yard with no signal into a browser tab. If the work is a local file or a report that has to leave a phone, we say so and take it to desktop or mobile. Showing it in a tab “because it's easier to demo” is how operations break later.

At handover the company owns the repository, the deployment procedure and the list of who can publish a change. The domain and the infrastructure accounts are created in your name. There is no Veodar console that Monday morning depends on.

If another team wants to take over in a year, they can read the code and the guide without asking us. That guide names the variables, how to roll back a bad release and who gets alerted when something fails. Without it, the project isn't delivered, even if the screen works on our laptop.

Maintenance, if you hire it, names what gets watched: errors, backups, certificate expiry, a small rule change. It isn't a bag of new ideas. New ideas are a new scope, with their own list of what's in and what's out.

The first release is the screen that, if it didn't open tomorrow, would have someone sending an email that same week. It isn't a map of every department. We'd rather ship that usable slice and grow than deliver a twelve-module program nobody uses.

The proposal states what's in, what's out and when people who aren't in the meetings get to see it. That text is the contract of expectations. If a system that “we'd also have to touch” shows up mid-project, we stop and decide whether it goes in now or waits.

Integrations are checked first. If the ERP only exports a file overnight, the scope states that rhythm and doesn't promise a real time that doesn't exist. Promising it is how the portal ends up pretty while the data keeps being born in a spreadsheet.