What we build
Four services. One connected system.
We do not sell isolated parts. A beautiful site nobody finds is useless. Ranking without anything clear to say is no better. And automating a process nobody thought through only speeds up the mess.
Almost every enquiry arrives naming a service: «I need a website», «I need SEO», «I want to automate this». Almost none arrives naming the problem: nobody understands what I do, I answer the same question ten times a day, people visit the site but nobody writes. The right service comes out of the problem, not the other way round.
That is why the four hold each other up. Strategy decides what to build and what to leave out. Design builds it and makes it understandable. Visibility makes it exist for the person already looking. And automation takes the repetitive part away, so your time goes to what actually needs judgment.
You can hire just one, and often that is the sensible move. Below, each one is explained in detail: what it includes, when it makes sense, and what we will not promise you.
Interface / Experience
Web Design & Development
We build the place where your business actually lives. Phone first, because that is where people will see you, then larger screens.
A website is not a brochure. It is the one thing of yours still working at three in the morning, when somebody searches for what you do and decides in a few seconds whether you are useful or whether they move on. Everything we do here is aimed at those few seconds.
The work starts with structure, not colour: what a person needs to understand, in what order, and which action we want to make easy. Visual design comes next, and code last. In that order, because changing a structural decision once screens exist costs ten times more.
And we do not start from zero every time. If you already have something, we begin by seeing what works, what gets in the way, and what is worth keeping.
How it gets built
- StructureWe decide which pages exist, what each one holds and how they link. This happens in text, without design: reordering a list is cheaper than rebuilding a screen.
- InterfaceWe design on top of that structure. Visual hierarchy, typography, space, and the states people actually meet, including empty, loading and error.
- CodeWe build with attention to performance, loading stability and accessibility. What appears fast and does not jump while loading keeps people; what lags or shifts loses them.
- ReviewWe check on mobile, tablet and desktop before publishing: overflow, contrast, touch target sizes, keyboard navigation and console errors.
What it includes
- Information architecture and page hierarchy
- Interface design for mobile, tablet and desktop
- Development with attention to performance and loading stability
- Copy organised to be read, not to fill space
- Baseline accessibility: contrast, keyboard navigation, touch target sizes
- And a clear path to contact
What we do not promise
We do not guarantee a number of visits or customers. That depends on your market, your offer and your consistency, not on the design.
Content / Discovery
SEO & Visibility
Being found is not a trick. It follows from having useful pages, well organised and understandable to a machine that reads them without seeing them.
A search engine does not see your page: it reads it. It does not know that photo is your shop, or that the blue block is a button. It knows what text is there, how it is titled, which other pages it links to and how long it takes to appear. That is where everything is decided.
We work both sides. The technical one, so your site can be crawled, understood, and does not block itself. And the editorial one, so it answers real questions, written the way people write them and not the way a manual would.
The editorial side is the one almost nobody does. A page that properly answers one of the questions you get by phone is worth more than repeating your keyword twenty times: the first is useful to somebody, the second only repeats.
How it works
- InventoryWe look at which pages exist, which get crawled, which are indexed, and which compete with each other saying nearly the same thing.
- TechnicalTags, canonical, hreflang when there are languages, truthful structured data, sitemap and robots. So nothing blocks what should be visible or exposes what should not.
- ContentOne page per intent. Titles and descriptions that say what is inside, and internal links that connect what genuinely relates.
- MeasurementSpeed, visual stability and errors. And then patience: indexing is not immediate and nobody controls it.
What it includes
- Technical review: crawling, indexing, tags, canonical, truthful structured data, sitemap
- Content structure and internal linking between related pages
- Unique titles and descriptions per page
- Speed and visual stability review, because they shape the real experience
What we do not promise
We do not promise positions, first pages or timelines. Nobody honest can. Structured data helps a search engine understand an entity, but does not guarantee rich results, and a sitemap helps discovery, but does not guarantee indexing.
Clarity / Direction
Digital Strategy
The part almost nobody hires and almost everybody needs. It decides what to build before building it.
Without it the same thing always happens: a website gets commissioned, sections get added because we are already at it, and by the end nobody knows what that website was supposed to achieve. So it gets judged on whether people like it, which is the surest way never to know if it works.
Here we connect six things: the business goal, who you are talking to, the message that holds that goal up, the content that proves it, the experience that carries it, and the action you expect at the end.
Each one constrains the next. Change the goal and the audience changes; change the audience and the message changes. That is why they are decided in this order and no other, and why whatever is unnecessary gets dropped here, while dropping it is still cheap.
How it gets decided
- GoalWe write down what has to happen for this to have been worth it, in terms you can check without depending on us.
- AudienceWho you are talking to, what they already know, what worries them and which words they search with. Not an invented persona: the questions that actually reach you.
- Message and proofWhat you claim, and what backs it. A claim with nothing behind it is advertising, and advertising gets discounted automatically.
- PrioritiesWhat goes into the first version, what can wait and what gets dropped. It is the uncomfortable part of the conversation and the most useful one.
What it includes
- A goal defined in terms you can measure
- A map of your audience and the questions they ask
- Priorities: what comes first, what can wait, and what to drop
- Content architecture
- And decision criteria, so later choices do not depend on the mood of the day
What we do not promise
We do not deliver a hundred-page plan nobody reads. The output is short and actionable, or it is not worth doing.
Process / Connection
Automation & Artificial Intelligence
Software and AI applied to real business tasks, with human judgment where it matters.
The rule is simple: we automate what is repetitive and predictable, and leave to a person whatever needs judgment, context or responsibility. Automating a delicate decision is not efficiency, it is risk.
The right question is not «can this be automated?». Almost anything can. The question is how many times a month it happens, what it costs each time it goes wrong, and who answers when it does. Those three answers decide it on their own.
And there is one condition we do not negotiate: anything that reaches a customer passes through a person first. The machine prepares, sorts and proposes; you sign.
How we decide what to automate
- FrequencyHow often it happens. Once a month and automating it costs more than it saves, so we do not.
- RiskWhat happens when it goes wrong. The more expensive the mistake, the closer the person reviewing has to be.
- ConnectionWhich tools you already use and how they talk to each other. Most lost time is spent copying data from one place to another.
- DocumentationWhat each workflow does, where to touch it and how to switch it off. An automation nobody knows how to stop is a problem waiting.
What it includes
- Finding the tasks that consume time without adding judgment
- Connecting the tools you already use, so information is not copied by hand
- Workflows with a human review point before anything that reaches a customer
- And documentation of what is automated, so it does not depend on someone remembering how it works
What we do not promise
We do not replace your team, and we do not apply AI because it is fashionable. If a task does not repeat often enough, automating it costs more than it saves, and we will tell you so.