Services · Websites and digital systems
Websites that are part of the company’s system
A website that only presents the company is a cost. A connected website is an entry point into your processes: a submitted request is validated, lands in a system, triggers a confirmation and a task for someone. We build the second kind, because the first produces nothing measurable.
Our position
We do not sell "beautiful websites". Design matters, but it is a condition, not the proposition.
What matters is what happens after someone submits a form. On a brochure site the answer is "an email arrives, which someone may read". In a connected system the answer is a defined path, with state, confirmation and an owner.
How you recognise it
- Requests from the site land in an inbox and get lost among other mail.
- You cannot say how many requests came in last month, or where from.
- Form data is copied by hand into another system.
- Nobody receives an automatic confirmation, so clients call to ask whether it arrived.
- The site cannot be edited without asking someone outside the company.
What a connected website means
Select a step for detail.
Request captured properly
The form validates on the server, not only in the browser. The required fields are the ones that make the request usable — not everything we could ask for. The more it asks, the fewer complete it.
Validation and protection
Server-side checks, spam protection without a CAPTCHA at first, rate limiting. A form flooded by bots becomes useless even if it works technically.
Stored with an identifier
Every request gets its own identifier and lands in a system — a structured spreadsheet is enough at the start. Without an identifier nothing can be tracked.
Google Sheets · CRM · database
Confirmation to the client
A message containing what they sent, the reference number and what happens next. Confirmation reduces chasing calls and is the first signal that the company runs in an orderly way.
Internal notification
To the address that is actually read, with the full context: what they asked, where they came from, which pages they read first. A direct reply from the inbox reaches the client.
Attribution context
First page visited, source, campaign. No PII and only under consent. That tells you what works, not just how many came.
Failure without loss
If the email does not send, the request stays stored and the delivery failure is visible. A site that shows "sent" without having saved anything is worse than a site with no form.
Reference architecture — not a client result.
What affects the cost
The number of real pages, not the number of sections. A page with its own content costs; a variant of the same page does not.
The number of languages, because each language is content written by a person.
The systems it connects to. A form writing to a spreadsheet is simple; a form that must write to an ERP, check stock and generate a document is an automation project, not a web project.
Frequently asked
Do you do the design too?
Yes, but in this service design follows function. If what you primarily want is a new visual identity, say so explicitly — that is a different conversation with a different goal.
Can we edit the content ourselves?
Yes. The structure is built so text can change without touching code. What we do not recommend is being able to change page structure unreviewed, because that is where internal links and indexing break.
Will you migrate our existing site?
Yes, with an old-to-new URL map and redirects. No indexed URL disappears without an explicit decision — otherwise you lose rankings you already earned.
How long does it take?
It depends on the number of pages with their own content and the systems connected. We do not give a timeline before the audit.
Other solutions
Want to find out whether your process is worth automating?
Free initial audit, 60–120 minutes. No obligation to implement. If automation does not make enough economic or operational sense, we will tell you.