Capabilities
Four capabilities.
One shared direction.
We only switch on the ones each business actually needs.
Growth
Experience
Intelligence
Capabilities
Technology · Web development for businesses
We build corporate and commercial websites, online shops, private areas and platforms with functionality of their own. We start with what you sell, who buys from you and how your team works, and only then choose what to build it with: WordPress or another platform that fits, the site you already have, or custom development.
What the business needs
Make it clear what we sell, be found by the people looking for it, and get enquiries to whoever answers them.
What decides the approach
What you need is already well solved
Something no platform brings ready-made
One need, two different decisions. What separates them is the business, not a preference for one technology.
The starting point
Hardly any company hits the limit all at once. They notice it in the enquiries that never arrive, in the ones that arrive without saying what they want, in the paragraph nobody on the team can change, and in the work that piles up around the website.
What an enquiry goes through before it reaches anyone
Six steps between what you sell and the person who wanted to buy it. Not one of them was designed looking at the next.
How it shows
The websites we build
Four kinds of project, from the surface inwards. Most companies need the first or the second; some need all four, and almost nobody needs them all at once.
What people see
to explain the company, order its services and get the right enquiry through
What people buy
to sell and to order the buying experience around the real catalogue and the real operation
This is where what any visitor sees ends
What people use
when someone signs in, looks up what is theirs and gets something done
What decides and connects
when there are rules, calculations or tools the website has to talk to
And this is where the project stops standing alone
When the weight is on how the site is understood and moved through, when the project is mostly a shop, or when the problem leaves the website and lands in how the company runs, we handle it inside the same project: Web design, Ecommerce and Custom software. You do not need to change supplier to cross that line.
What we build it with
Not everything has to be built from scratch, and not everything fits inside a platform. The same need, as it gets more specific, is met by something different — and the decision is made by looking at the business, not at the technology list of whoever builds it.
The business adapts to the tool
Let people browse the catalogue and buy online.
The need is a common one and there are platforms that solve it well: WordPress or another content manager, a commerce platform, a third-party tool. The work is in the structure, the design, the content and in leaving it in the team’s hands — which is a good deal of work, and it is the part that decides whether the site works.
In exchangeYou work the way that platform works, so you have to know it before choosing it.
Let people browse the catalogue and buy online, with each customer’s own price and discount.
The platform does the job and what is missing is one specific part: a flow, a calculation, a screen, a permission, an integration nobody brings ready-made. We build on top of what is there instead of replacing it — WordPress and custom development are not mutually exclusive.
In exchangeYou inherit the good and the bad of that platform.
Let people browse the catalogue and buy online, with each customer’s own price and discount, and have the order respect their credit limit and delivery terms.
The rules are your company’s now and nobody brings them ready-made: your own pricing, statuses, validations, permissions, processes that only make sense there. That is when building stops being a luxury and becomes the cheap option.
In exchangeYou decide everything, and you maintain everything too.
The tool adapts to the business
If a tool that already exists does the job well, we will say so and set it up. Charging to build something that is already built is not custom work: it is expensive work.
When the project calls for it
Not every website needs this. When one does, the visible part is almost always the smallest: what makes it pay is what happens after the click, and above all what happens when nobody is watching.
What the customer does
An account customer presses ‘Confirm order’.
What the system does
And afterwards, with nobody watching
If the credit limit will not stretch, the order is not rejected: it is held, and accounts sees it before the customer does.
For the customer it was one click. For the business it is nine decisions nobody takes by hand any more, and three pieces of data nobody types twice.
When the website stops standing alone
Something entered through the website should not be typed again into the CRM, the ERP, the accounts or a spreadsheet. It is entered once and it travels. That is where a website stops being a separate piece and becomes part of how the company runs.
How we pin it down
At the start, almost nobody knows exactly what website they want: they know the business and they know the problem. The work is closing down everything that could still mean anything at all, until what is left can be checked.
‘We need a new website; this one no longer represents us.’
That is a goal, not yet a website. Nothing here can be quoted without making it up.
8 questions still open
‘Eight services, three sectors, and the quote request goes to the rep for that area.’
The exceptions show up, and so does who will keep this running — which is where the real project is.
4 questions still open
‘From a service page you can request a quote, and it arrives with the service and the area on it.’
It is tried with real content before anything is built around it. Changing something here costs an afternoon; changing it at the end costs the project.
1 question still open
People find it, understand it, request a quote, and the team publishes without ringing anyone.
And from here it grows in phases, on a base nobody has to rebuild.
Nothing is left open to interpretation
What cannot be checked is not defined yet. That is why a project is scoped before it grows, and not the other way round.
Published work
They do not all ask for the same thing. These three are published and you can open them: a commercial structure that grows city by city, a website that brings work to a renovation company, and a platform with rules of its own.
Two company websites
Here the website is the channel: someone looking for a taxi in their city has to find a page that speaks about that city. We built the structure that makes that expansion possible, one page per city, without turning it into a bigger website.
Here the website has one job: explain what the company does, show finished work and bring in quote requests. The same project later carried on inside the business with a custom panel, but the public site stands on its own.
Neither of them needed a platform to do its job.
And when a project needs to go further.
What it had to do
Rooms with slots and capacity, real availability at every moment, bookings made by the end customer and bookings created by the team, payment with its amount and its method, and a status that means the same thing wherever you look at it from.
What was built
A multi-company system where availability is what rules: the public widget only offers what is genuinely free, the panel shows the whole month by room and by status, and a booking created by hand comes in through the same door as one made online. There are no two versions of the truth to reconcile afterwards.
In productionKonevent is a live product, not a prototype.
Real screenshots of all three products, with demo data in the panels.
Not every company asks for this level of development. We show it so you know it is there, not because you need it to work with us.
Where we fit
We work on
You do not have to bring a complicated project. Most of the websites we build have to explain clearly what is sold and bring in enquiries; the rest of what we can do is there for the day the project asks for it.
Frequently asked questions
Yes. For many corporate and commercial websites it is the right platform: the team manages the content without depending on anyone, there is an ecosystem for almost everything, and the project goes live sooner. What we do not do is install a template and hand it over: the structure, the design, the content and the way it is managed are planned around that particular business. And when something comes up that WordPress does not bring ready-made, we build it on top instead of throwing the platform away.
When the rules are already your company’s and nobody brings them ready-made: your own pricing, permissions, statuses, validations, calculations or processes that only make sense there. Also when the cost of forcing a platform to do something it was not designed for is higher than building it. An advanced form, an integration or a calculation do not on their own mean starting from scratch; what does is the sum of them.
The decision comes after understanding the business, not before. What weighs is the goals, who is going to manage the site and how comfortably, which integrations are needed, what maintenance it will take, the budget, and how it is expected to grow. If the answer is a platform that already exists, we say so; if the answer is to build, we argue it with those same criteria and not with a technical preference.
You almost never have to start from scratch, and when we do propose it we argue the case. We can build on what is already there, replace only the part that limits you —a flow, a panel, an integration— or build a new core and migrate in phases. Redoing everything only pays when the current base costs more to maintain than to replace: anyone who opens by proposing to throw it all away is usually selling hours, not judgement.
You do, and that is decided at the start because it shapes what the site is built with. We define what the team has to be able to change without ringing anyone —copy, services, projects, prices, notices— and the management side is built around that list. A website only its builder can touch ends up out of date, and a website that is out of date stops selling however well it was made.
It depends on the scope, the number of business rules, the integrations, and whether there are users, permissions and statuses involved: a corporate website does not cost the same as a platform with a private area, payments and a connection to an ERP. Phases are possible and on most projects they are the better option: a core that already earns its keep is defined, published, and grown on that base. What we always do is scope before giving a number.
Yes, and it is often the very reason a project is built to measure. The website can connect over an API to the CRM, the ERP, the payment gateway, the accounts, the shop or internal tools, so that a piece of data is entered once and travels on its own. Where there is no API, we look at what route is possible and say plainly what can be automated and what cannot.
Scope, ownership and terms of use are put in writing before we start, and on a business project the normal arrangement is that the code and the data belong to the client. Afterwards, every digital system needs maintenance: updates, security, performance, adjustments and new functionality. A website is not finished the day it is published, it settles down and keeps growing with the company.
Let’s talk
You do not need to bring a technical brief, or to know what it should be built with. Tell us what you do, what you want the website to achieve and who is going to manage it, and we can tell you how the project would go and what it makes sense to build it with.
We use cookies to understand how the site is used and to measure whether our ads bring enquiries. They stay off until you accept them, and we do not use them to profile you or follow you around with ads. You can choose each purpose separately. More in the cookie policy.
