Two founders —development and business on one side, marketing and communication on the other— plus a network of specialists we bring in depending on the scope of each project. We're not a big agency and we don't pretend to be: what you get is that whoever studies your case is the one who builds it and the one who answers for the result. No subcontracting chain.
We work like a product and business team, and it shows in the order we do things: real demand data first —what people search for, how much volume is there, how they phrase the need— and only then a decision about what to build. And what gets built is a connected system —website, positioning, campaigns, agents and management systems— instead of scattered tools nobody ties together. Metrics are defined up front, and if something isn't moving the business, it changes.
Yes. The best-proven case is healthcare: businesses with a native-code website, positioning and Google Ads campaigns, with a real increase in patient flow. You will find them on the home page, with their logos. And you are looking at the most honest example right now: this site and the AI agent that answers on it are K3A products, built with what we sell.
We work in Spanish, with businesses in Spain and across Latin America, and everything is remote — we don't need to be in your city. That is why the pricing page carries two lists, one per market: where your project is based changes what it costs to operate, and we'd rather say so up front than bury it inside a quote.
Everything that is yours, and it was yours from day one: the domain, the code and the Google accounts are in your name, and K3A works with delegated access, never with your passwords. If the relationship ends, you keep the accounts, their entire history and the work itself. That is deliberate: we'd rather you stay because the work pays off.
It doesn't. GEO stands for Generative Engine Optimization: the work of getting the AI assistants that answer questions and recommend solutions —ChatGPT, Gemini, Perplexity— to cite you and link to you when someone asks them about what you sell. And it is not just getting named: more and more they answer with linked lists of recommendations, so being on that list brings visits the same way being on Google does. SEO puts you in the list of results; GEO puts you inside the answer. Both are worked together, on the same site and the same content.
Months, not weeks, and it is better to know that going in than to find out later: organic positioning builds up over time and there is no honest way to rush it. What you do see early is the work itself —the research, the technical fixes and the first movements in the reports—. And if you need customers this week, that is what Google Ads campaigns are for, while the organic side grows.
No. Rankings are decided by Google's algorithm, they shift on their own, and nobody outside Google controls them: whoever works on your site influences them, they do not command them. What does get committed is the work and the numbers: research on real demand data, technical fixes, content written to get you cited, and ongoing measurement. If something isn't moving the business, it changes — and you will have the data in front of you to check it yourself.
Ads bring customers from day one, and they stop bringing them the day you stop paying. Positioning takes months, but the visits it earns are not paid for and they keep coming afterward. They are not alternatives: the usual play is to switch on ads for movement while positioning matures, and to depend on them less and less. If you can only take on one right now, that gets decided with your market's data, not by a rule of thumb.
It is the digital market research done before anything gets touched: what people in your sector search for, how much real volume is there, and how they phrase that need. The strategy comes out of it — and so does an honest answer about whether it is worth going on. It is billed separately because it is work that stands on its own: you keep the research even if you do not continue. And it is deductible if you take on other services afterward, under the terms you will see on the pricing page.
A chatbot picks from answers someone wrote in advance. An agent reasons with your business knowledge loaded inside it, and it also acts: it books on your calendar, logs to a spreadsheet, sends the email. It answers over chat, voice notes and phone calls, at any hour, and it runs with guardrails so it can't step outside what you authorized.
It is not used to train models, and that is not a promise of ours: it is a feature of the enterprise tier of Google's Vertex AI, which is different from the consumer versions the public uses. The data stays yours —you decide what it is processed for— and K3A acts as a data processor, under a written contract that sets out what can and cannot be done with it. Each client is isolated from the rest at the database level, and the agent does not ask for health data or any other special category. If you sign, you also get the full technical sheet: where it is processed, who else is involved and how long it is kept. What we don't do is write your privacy policy: we hand you the facts, and your own advisor reviews them.
Passwords, never: we don't ask for them, we don't store them, and the same goes for the seed of your two-factor. We always work with delegated access, which Google's tools already offer out of the box and which you can revoke yourself whenever you want, without telling anyone. And the access granted is the minimum the agent needs for what you ask of it: if all it has to do is book, all it sees is the calendar. This rule protects you before it protects us — if we signed in as you, the logs could not tell what the agent did from what you did.
That is what the guardrails are for: written limits on what it can say, what it cannot, and how far it can act. It does not improvise prices or commitments, and when a question falls outside its script it hands the conversation to a person instead of making something up. Every conversation stays auditable, so you can read what it answered and fix the script. And decisions with consequences are still your team's: the agent answers, collects and books — it does not grant or deny anything.
Because they are two different things, and rolling them into one number would be easier to sell but less honest. The monthly fee is your agent: its upkeep, its adjustments and its channels. Platform usage is what the AI behind it costs, and it works like this: no cap on conversations, you pay for what you use, and a single day has a ceiling. That is why the day you handle a thousand people does not get away from you. The pricing page has a table of approximate ranges by budget, so you have an idea before you sign anything.
To Google, straight from your own Google Ads account, which is in your name. K3A charges for managing the campaign and works with delegated access. That way you see where every euro goes — and if you ever stop working with us, the account and its whole history stay with you.
There is no single number that works for everyone: it depends on what a click costs in your sector, and that varies a lot from one market to another. What there is, and it is worth knowing up front, is a floor: the daily budget has to be enough for several clicks a day. Below that the campaign does not gather enough data to decide anything — you pay, but you don't learn. The number for your case comes out of the research, before anything gets switched on. And remember that spend is yours and goes to Google: the management fee is separate, and it is on the pricing page.
Because on budgets of tens of euros a day there is no room for the system to experiment with your money. Every euro spent on a headline nobody wrote or a keyword nobody asked for is a euro that doesn't bring a customer. So automatically created assets stay off: Google can only combine material we wrote. What you get out of that is knowing exactly what your ad says every time someone sees it, and that matters when the sector is a sensitive one or third-party brands are involved.
We look at what is business, not at what looks good: real leads —messages, calls, forms—, what each one costs, which searches bring them, and what share of clicks ends in a lead. If that share is not going up, there is no business, and you get told. From your side we only ask for counts, never records: how many appointments or sales there were each month, where they came from and for which service. No names, no phone numbers, no histories — four numbers a month is enough to line up the real result with the campaign, and it means we never have to enter your system or handle your customers' data.
First we audit the one you have: how it is structured, which keywords it uses, what the people reaching you are really searching for, and where the budget is going. That is what decides whether it gets fixed or rebuilt, and you get told with the data in front of you instead of it being rebuilt as a matter of course. What turns up again and again is budget leaking into searches that are not your customers, and cleaning that up tends to be the most profitable work in the whole setup, without putting in another euro. What is not part of the management is rebuilding the website: if that is where the problem is, it gets quoted separately, with the scope in writing.
First we check whether the one you have converts, because ads pointed at a site that doesn't convert burn money. If it converts, we work on it: when it's built in native code, there's a positioning setup for sites that already exist. And if the site itself is the problem, you'll see it in a separate quote with the scope in writing, not in a surprise invoice.
It means the design is working for you before anyone reads a paragraph. In the first few seconds a visitor is not reading: they are looking, and deciding how they feel. So that is what the design is built for — catching their attention and carrying the emotion your brand wants to leave behind, whether that is trust, approachability or solidity — through color, imagery, pacing and the order of what gets seen first. The copy comes after, and it backs up the same thing. And this is not about looking nice: every decision is made with conversion in front of it, because a website people like and do not act on has done nothing for you.
It means the site is written by hand, with no layers of intermediate software to load on every visit. What you get out of that is three concrete things: it loads fast —and speed is both user experience and positioning—, it can be structured the way a search engine needs instead of the way a tool allows, and it comes ready to plug automations or an AI agent into whenever you need them. What it does not come with is a dashboard for you to tweak it every afternoon: if that is what you want, say so at the start and it gets decided with that on the table.
It is built so that nothing goes out to a third party before the visitor allows it, and that is harder than it sounds: a font or a script loaded from another company's server sends your visitor's IP address before the cookie notice has had a chance to ask them anything. So the assets are served from your own domain, and the notice genuinely governs the analytics and advertising tags: if the visitor does not accept, they do not load. This very site is built that way, and you can check it.
Because “a website” can be five pages or fifty, with the copy written or still to write, with one integration or four. Giving a fixed number without knowing that means either padding it just in case or coming in short and cutting corners later. What does get fixed is the scope: before quoting, we settle which pages, which copy and which integrations are in, and that goes in writing. From there the price does not move, and anything asked for on top gets quoted separately instead of showing up on the invoice.
It doesn't need to go through the stores: it's built as a progressive web app and installs on phones and desktops straight from the browser, with its own icon. It updates itself, with no review queue to wait on. If your case really does need to be in the stores, it can be packaged for them.
Usually yes, and if that is your case we will tell you. Before anything gets built we check whether a standard tool solves your process, because it works out more cost-effective for you: maintaining it is not your problem, and the price is spread across thousands of customers. Custom makes sense once you have tried the standard route and there are steps in your operation no off-the-shelf program covers well, or when the patch you rigged up to cover it no longer holds as you grow. And if what you actually need is a CRM or an ERP set up and tailored, that is another of our services and it is usually the shorter road.
Yes, and these days without going through the stores. Installed from the browser it behaves like an app —its own icon, full screen, no address bar— and from there it reaches the camera, location, and uploading and downloading files, on Android and on iPhone alike. Notifications too, with one iPhone detail worth knowing: there they only arrive if it is installed on the home screen, not from a Safari tab. Packaging it for Google Play and the App Store is done for a different reason: so it can be found in the store, or when your case needs something the browser still cannot reach, such as Bluetooth or NFC.
The app, no. The process, yes. You don't have to arrive with the whole tool worked out: we start by building the minimum that already creates value for you, your team tries it, and it grows with use. What you do need is to be clear on the process you want to digitize, because digitizing a mess leaves it just as messy and more expensive to change. If it isn't clear yet, we put that in order first — and sometimes that is where it turns out the bottleneck was solved by a simple integration and needed no app at all.
Writing the code is the part AI already does well, and we use it too: nobody here is selling hours of typing. What it doesn't solve on its own is what comes before and after: understanding your operation well enough to know what to build, deciding what NOT to build —which saves more money than the first part— and answering for the result on the day something breaks in the middle of your working day. If you have the process clear and the appetite to wrestle with it, go for it, genuinely. If what you want is for the problem to go away and for there to be someone to call, that is what you are hiring here.
A CRM keeps order in what happens with your customers: who asked, where they stand, what they were promised. An ERP keeps order inside the company: sales, purchases, invoices, inventory. Almost no small business needs both at once — you start where it hurts most, and leave it ready for the other one to come later.
Mainly Notion, Zoho and Odoo, and depending on the scope we can consider another technology. But the tool gets picked at the end, not at the start: first we map how your business actually runs and what you need to be able to see, and that is what decides which one fits. Picking it first is how you end up with a business bent out of shape to fit a program. And if you already have a preference or a licence for one, we start from there and tell you whether it works for your case.
Not necessarily, and the first job is to find out whether the problem is the tool or the process that was put inside it, because those are not the same thing and they do not cost the same. So we map how you actually work and clean it up: removing the steps that are not needed before digitizing them. Then we decide whether what you have gets reconfigured or replaced. Switching systems without fixing the process just moves the problem to a different screen.
That is the real risk with these projects, which is why go-live does not end on handover day: we leave the system ready to run, we train the team, and we adjust it against real use over the first few weeks — which is when whatever worked in theory and gets in the way in practice finally shows up. And there is one part we cannot supply: if the plan is to install a CRM without changing any habits, it will not work, and we would rather tell you that than charge you for it.
Because they are two different jobs. Implementation is setting the system up around your process: configuring it, defining stages, permissions, views and reports, and leaving your team using it. That work is known, so it can be quoted against a reference. Custom development means programming something the system does not do out of the box, and there the price depends on exactly what it is: we look first and quote after. What we don't do is throw out a number and revise it halfway through.
In most cases yes, because today's tools usually have a door built in for other programs to use. The first part of the job is checking that on yours and telling you before we quote: if one of them won't connect, we look for the route that does exist, or we tell you there isn't one.
We start by measuring where the time goes and where the mistakes happen, and we order the work by what gives the most result for the least effort, not by what looks most impressive. The boring stuff comes first: the figure that gets copied from one place to another, the alert somebody has to remember to send, the report that gets built by hand every week. And there is an honest filter: if a task takes you five minutes and you do it twice a month, automating it does not pay for itself. There has to be enough volume for those five minutes to add up by the end of the month.
For a single step, often yes, and if that is your case we will tell you. The difference shows up once the process has several steps, exceptions and different people involved: connecting one thing to another is no longer enough. A flow is designed with four pieces —what triggers it, what it does, how you check it happened, and who owns it if it didn't— and those last two are what get left out when something gets rigged up in a hurry. An automation nobody is watching is the one that leaves you stranded in the month that matters.
It depends on your case, and since it affects you it gets decided with you. If you already have your own tools, it normally lives in your account: your credentials, your control and your invoice, and we charge for designing the flow. If you are a small business with nothing set up yet, it can live on our infrastructure and we run it —it is not opened up to third parties, for security— and in that case it goes inside the price, because it is a recurring cost and risk we take on, not a favour thrown in.
That is the right question, and the answer depends on what triggers the flow. Anything that starts from an event —an enquiry arrives, something gets paid, someone fills in a form— fails loudly: you notice the same day, because somebody was waiting for that alert. Anything that starts at a set time fails silently: Monday's report simply does not arrive, and weeks can go by before anyone connects the two. That is why every flow has it written down who owns it if it does not run, and why anything that depends on the clock is built in your account, where you can see it too.
Because where your project is based is part of the brief, not a discount: purchasing power and the cost of operating are different in each market. On the pricing page you pick where yours is and see the list that applies to you, with both on screen so you can compare them.
We work it out from your device's time zone, not from your IP address: that way nothing of yours gets read and there is nothing to store. And it is a preselection, not a decision — the selector is always in view and you change it with one click. Both lists are on the page at the same time, so you can compare them without taking our guess on trust.
Because they are two different things and it is worth keeping them apart. A price without “from” is an exact amount: that is what it costs. A price with “from” is a floor, not a ceiling, because that work depends on how complex it turns out: we start there, and the final figure comes out of the scope we agree in writing. We keep the distinction instead of putting “from” on everything, which would be the easy way out, because then no price on the page would mean anything.
Because K3A always invoices in euros, and quoting in one currency to then invoice in another makes you convert twice and leaves the feeling that the price changed along the way. With both lists in euros, what you see on the page is what the invoice will say. And the adjustment for your market is already inside the list: you don't have to go looking for it in the exchange rate.
The terms go in the quote, in writing and before we start: amount, scope and dates, so there is nothing to discover later. And yes, we can work out a payment plan if you need one — say so when we quote and it gets built in there. The flip side of a closed scope is that anything not in that quote does not show up on the invoice: if you want to add something halfway through, it gets quoted separately and you decide.