Common questions

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. Throughout the project you talk to the person who does the work. The size varies: I have built a site for a one-person business and 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 work remotely, in Polish and English, with companies in Poland and abroad. We start with a short description of your project. You then receive a scope, quote and next step in writing. We agree how the work and delivery will run, wherever your company is based.

Yes. WordPress repairs start at PLN 290 net. I also take on single pages, integrations and fixes to existing systems. We agree the scope and price before work starts. Anything outside that scope needs a separate agreement.

For a small project a freelancer is usually simpler to manage and cheaper, and an agency makes sense when the work needs several people at once. Here you talk to the person who does the work, throughout the project and after it. I also work white-label for agencies, as their design and delivery side. You get the scope and the price in writing before anything is signed.

I quote an agreed scope of work. A landing page with a form starts at PLN 2,500 net, a company website of up to three pages costs PLN 3,500 net, a WooCommerce store of up to 30 products PLN 8,500 net, and a migration to Shopify of up to 500 products PLN 3,900 net. WordPress repairs start at PLN 290 net. Other projects are quoted after the brief. You receive the price, scope and exclusions in writing. Ongoing support is described in the care section of the website pricing article. Work beyond the hours included in a monthly care plan costs PLN 280 net per hour. For Google Ads, Google bills your ad budget directly and my invoice covers campaign management.

What a simple company website costs ↗

I pick WooCommerce when the site and the shop should be one place, run from one panel, and Shopify when the shop is the whole business, with a theme written from scratch. A WooCommerce shop of up to 30 products costs PLN 8,500 net. A Shopify shop built from scratch is quoted after the brief, and moving an existing shop to Shopify, up to 500 products, costs PLN 3,900 net. I recommend one after reading your description.

WooCommerce shop pricing ↗Moving to Shopify ↗

Asystent PV, the chat assistant for solar companies, costs PLN 3,900 net to set up plus PLN 690 net a month. For another industry I quote after reading the questions your customers ask, because they set the scope. I usually start with the website alone and add a calendar or CRM connection once the questions show what people really ask.

Chatbot for business: prices and scope ↗Asystent PV ↗

I quote an application in writing after the brief, because the price depends on the number of user roles, the systems it has to work with, how much data has to be moved and how many languages it runs in. A simple data panel and a learning platform with roles, payments and certificates are very different jobs. I start with a first stage small enough for you to judge my work before you decide on the rest.

Web applications ↗

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 every further page in the same layout is cheaper than 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 differ widely in the work they need. 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 can work alongside your team in an existing project or take responsibility for one module. I start with a code review and agree how we will work together. If I find bugs or security issues, you receive a list. We agree which fixes need to come first before new features are added.

I give you a timeline after reviewing the scope, before work begins. It depends on the features, integrations, languages and whether your content and data are ready. My reply to the brief includes a proposed schedule and a list of materials I need from you. Larger projects are split into stages so you can assess a working first part before commissioning the next.

At handover you receive the agreed access, code and content editing panel, if one is included in the scope. We agree ongoing support, monitoring and development before launch: what the plan covers, what it costs and how to request changes. You know who looks after the system and which work you are paying for.

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.

I start with one process: its inputs, tools, decisions and exceptions. We agree how to measure improvement, such as handling time or error rate. I then build a small working version and test it on real examples. We also identify the actions that need human approval. The implementation grows once the first stage meets the agreed requirements.

It depends on the agreed configuration and connections to other systems. Hosting n8n on your own server keeps workflows on your infrastructure, but a connection to an external model can send data to that provider. Before implementation, we document which data is needed, where it will be processed and which providers will receive it. For sensitive data, we agree a local solution or a way to limit what is passed on. You approve the choice before launch.

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 choose tools to suit the functions you need and how you want to manage the system. I build editable websites on tools including WordPress, stores on WooCommerce or Shopify, and applications on React, Next.js or Angular. For automation I use n8n, Make or custom code. Before work starts, I explain the choice, running costs and how the project can be handed to another developer.

Yes. You own the advertising account and grant me access. Your campaign history and data stay in that account. We agree the budget and how to measure results before launch. Budget increases need your approval. AI can support analysis and suggest actions; a person approves decisions that affect spending. Reports use account data and agreed results, such as orders or enquiries.

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 about what you want to build or improve. Use the short brief or the details on the contact page. I reply personally. If a conversation is needed to agree the scope, we can arrange a time in my reply.

Describe your idea ↗The contact page ↗