Common questions about websites, shops, apps and AI

ENSOMEDIA is the brand under which I, Radosław Fedorczuk, design and build websites, online shops, web applications and AI implementations, and run Google Ads campaigns. I am a computer engineer with twelve years of professional work in IT, based in Wrocław. My company has traded since November 2018, a date anyone can check in CEIDG, the Polish business register. There is no subcontractor chain and no handover between departments, so the whole way through you talk to the person who knows your project. The size of the work varies, from a site for a one-person business to a learning platform used by 23 organisations and 804 accounts. I also run two products of my own: Asystent PV, an AI chat assistant for solar companies, and ShieldWave, a website security scanner. I test on them first what I later offer to clients.

I am based in Wrocław, Poland, and I work with companies wherever they are. Distance has never been the constraint. I work in Polish and English. The work runs remotely: a brief, a reply with a considered next step, and a report once something is live. Nothing waits for a free slot in a calendar. Delivery is remote as well, since what I build runs on managed cloud, Google Cloud Run or Vercel, and is monitored from wherever I am. A client in another country gets the same process as one on the next street.

Yes. The smallest job I take is a WordPress repair from PLN 290 net. Among new builds the smallest is a single page, and a simple website is one to three days of work. Most of what is published on this site is larger than that, which only reflects what I have written up so far. Small or large, you get the same person, an agreed scope and a fixed date. A first job does not have to be a whole system, and a small one is a normal way for a longer engagement to begin. The scope is written down before anything starts, so a small job stays small, and anything outside it is a separate decision.

I price scope, not hours, and the range comes in writing after the brief, before anything is signed. I do not bill projects by the hour: a price quoted before anyone has looked at the thing it is meant to fix is a guess, and guesses turn into change requests later. The only hourly figure I publish is PLN 280 net for work beyond the banked hours inside a monthly care plan, described in the care section of the website pricing article. What typical jobs cost, a simple site or an online store for example, is written out in the articles on the blog. The scope can be small. Sometimes a Zapier or Make integration does the job without custom code, and then I say so. Larger builds are quoted the same way: a range, plus a proposed first stage small enough to judge me on before you commit to the rest. For Google Ads, Google bills the ad budget straight to your account, and my invoice covers only the work.

Four things, in roughly that order of weight: how many roles the system has, how many other systems it has to talk to, how much existing content or data has to be moved, and how many languages it ships in. Page count matters far less than people expect, because pages built on one template are cheap after the first. A brochure site with five pages and one contact form sits at the bottom of the range; the same site in three languages, with a CMS the client edits and a CRM behind the form, does not. An application is priced on its roles and integrations, which is why two systems with the same number of screens can be a month of work apart. You get all of it back as a range after the brief, which is why the brief asks what it asks.

You do. Rights to what I build belong to the person who commissioned it, unless something else is agreed in writing. That is the default here and it does not need negotiating. The same principle runs through the rest of the work: the advertising account is registered to you and you grant me access to it, and at handover the admin panel and the CMS go to your team. If we stop working together, nothing of yours needs extracting from me.

Yes. I work alongside in-house developers, and I take over code I did not write: on your repository and your process, or with one module handed to me and handed back documented. One condition comes with that, and you hear it before the quote. If anything in the existing code is broken or insecure, that gets fixed first, before new features are built on top of it. It is usually a short list. Building over a hole you already know about means signing your name under a problem you did not create, and when it surfaces the first person asked is whoever touched the code last. So the work starts with a written list of what I found and a decision about which of it is fixed before anything new begins.

It depends on scope, and anyone who answers otherwise before seeing yours is guessing. Every figure here belongs to the scope written beside it, and none of them is a quote for a job nobody has looked at yet. A simple website is one to three days, depending mostly on revisions. A larger site is around two weeks. A Shopify store from scratch, with a theme designed for that store, a catalogue of around thirty products, one payment gateway and one courier, is two to four days including revisions, and I quote the price after a short brief. Moving a shop of up to 500 products to Shopify is a separate job with a published price of PLN 3,900 net and 10 to 14 working days. A larger migration, or a shop with a thousand products, an ERP integration or B2B pricing, is quoted after the brief. A first automation, meaning one process with a visible stake, is eight to ten hours, and that is where automation starts; a whole department takes a series of them. A web application is anywhere from seven days to six months. The range is wide because a simple dashboard is one job and an e-learning platform with roles, payments and certificates is another, and no single figure covers both honestly. Your timing is agreed in my reply to your brief, before anything is signed. The five stages are the same every time: Understand, Design, Build, Ship, Run it. The last one continues for as long as the system is in use.

Maintenance is part of the engagement from the start, so there is no separate service to buy after launch. At handover you get the admin panel and the CMS. After that I monitor what is running, fix what breaks and keep developing it, and I write the code so that whoever changes it a year later can follow it. I know how much work that takes from my own product: ShieldWave runs in production on Google Cloud Run infrastructure I maintain myself.

AI is worth implementing where a model takes real work off a named person today. So I start with an audit of the process: which process, what it costs now in time, volume, cost of error or customer experience, and whether ordinary software without a model would fix it more cheaply. Sometimes it would, and I say so. Where it clearly is worth it, an implementation looks like this: a supplier invoice reaches an inbox, the system reads the fields, checks them against the order, updates the CRM and routes mismatches to a person for approval.

It starts with one process and a map of it, in four steps. Pick one process where the stake is obvious: time, volume, cost of error or customer experience. Map the data, the tools, the decisions and the exceptions inside it before any model is named, since exceptions cause most of the breakage later. Build a small flow that runs in production: input, context, action, a human in the loop and a measure of quality. Then test it on real examples and extend it only once the base flow works. I build the workflows in n8n where that is the right tool.

It depends on where the data sits, and the split is a fixed policy that holds on every project. Sensitive data stays local. n8n is installed on your own server, so the workflow runs on your infrastructure and the data never leaves it. Where the data is not sensitive and both sides agree a hosted model is the sensible choice, one is used, Groq for example, and the provider is named before anything is built. Either way I build inside the systems you already run, and you make the choice, in writing. Beyond that, the third parties involved are the ordinary infrastructure ones and they are the ones already disclosed: hosting, a CDN such as Cloudflare, and analytics such as Google where a measurement tag is in place.

Yes. If you need an NDA before discussing details, say so in the brief and I will sign one first. It does not stop at the document. With agencies I work white-label, as the design and delivery side, and in that arrangement your client usually sees only your brand. The brief is handled on the same principle: it posts to a script on my own hosting and comes to me from there, so it never passes through a third-party form service, and what you write in it never reaches Google, Meta or OpenAI. I keep it for no more than 12 months after our last contact, unless the conversation turns into a project, in which case the paperwork is kept for as long as tax law requires. The privacy notice sets out the whole picture, including what is measured when you consent.

I build on standard, widely used tools, so another developer can pick up what you end up owning and you do not depend on me. I pick the technology against what has to exist: WordPress or WooCommerce where time and editing it yourself are what count, Next.js or Angular where the site stops being a site. The choice is part of the work. In practice: the part you click on is React, Next.js or Angular written in TypeScript; the part behind it is Node.js and Express; the data sits in a real database, PostgreSQL, MySQL or Supabase, with pgvector where a search has to match meaning as well as words; and it runs on managed cloud, Google Cloud Run or Vercel, with monitoring. Online stores are Shopify, with the theme written from scratch in Liquid, or WooCommerce where the catalogue belongs beside the site. Content is edited in WordPress or Sanity. If none of those names mean anything to you: they are the boring, well-documented choices, which makes them easy to hand over.

Yes, always on the advertising account you own, with agency access you grant and can withdraw in a minute. Five rules hold on every account. Your account, your data: the whole campaign history stays with you if we stop working together. A spending ceiling the system cannot raise: daily and monthly caps live in a controller outside the model, and raising one is a written decision by a person. Results are counted in confirmed orders: I optimise towards an order confirmed in the shop or an enquiry confirmed in the CRM. AI proposes, a person approves: anything that moves money is signed off by a human first. And the report is written, in the figures the account itself shows.

How I run Google Ads

Yes, I work on visibility in ChatGPT, Perplexity and Google AI Overviews. It stands on ordinary technical and content SEO and does not replace it. What changes is the shape of the content: a passage an assistant can quote has to stand on its own, be specific and be checkable. So I lay pages out that way, add structured data that tells a machine what it is reading, and publish a plain-text summary at /llms.txt for the models that read one. Then I check the result: I ask assistants the questions your customers would ask and record whether your brand comes up.

Write two or three sentences; that is enough to start. The brief has four short stages, takes less time than an email, and asks the things I would otherwise have to come back to you about. If a form is not your thing, the contact page has the other way in. Say what should change, or describe the work that eats the most time. I reply personally, usually within one working day.

Describe your ideaThe contact page