- Year
- Scope
- My role
FAQ The questions
The questions
that come up most
These are the answers I usually give in a first meeting: cost, timelines, who owns the code, and what happens once it is live. There is a glossary at the end in case any of the terms are new.
FAQ
Frequently asked
Frequently asked
questions
Short and to the point: how I work, what it costs and what to expect. Didn't find your answer? Write to me — I reply within 24h.
How much does a website or app cost?
Pricing is fixed and transparent — from a landing page to custom web apps and SaaS (quoted individually). Current rates in your language and currency are shown in the Pricing section. Every quote is free and delivered within 24 hours after a short project brief — no hidden costs.
How long does a project take?
A landing page ships in a few days, a store in 2–4 weeks, and a larger SaaS app in several weeks. I work in two-week sprints with weekly demos, so you see progress continuously and nothing surprises you at the end.
Do I own the code and the rights?
Yes. Once the project is paid, I hand over full economic copyright, clean documentation and the repository. Zero vendor lock-in — you can keep developing with me or anywhere else.
Are websites delivered with ready content?
Yes — sites ship with ready, professional copy and on-page SEO included. You don't get an empty template to fill in yourself.
Can one person handle an advanced project?
Yes — and it is an advantage, not a limitation. I work across the whole stack: analysis, UI/UX, backend, frontend, mobile, DevOps and deployment. No department handovers, no broken telephone, no coordination overhead. You talk directly to the person writing your product's code.
Which technologies do you use?
Next.js and Laravel for web back/front, React Native (Expo) for mobile, PostgreSQL/MySQL, Redis, Docker and CI/CD. I match the stack to your business goals and budget — not the other way around.
Do you offer post-launch support?
Yes. The Technical Care Plan starts at PLN 500/mo (3 development hours, bug fixing, updates, monitoring and a 24h SLA). Larger packages are available on request.
Do you help with SEO and performance?
Absolutely — technical SEO, Core Web Vitals, structured data and performance optimisation (target Lighthouse 95+) are my daily bread. It can be covered within a project or as a standalone audit.
Glossary
The words that come up when quoting
Technical jargon should never be the reason a conversation about your project stalls. Here are short, honest definitions of the terms you will hear from me — or from anyone else you talk to.
- MVP Minimum Viable Product
- The smallest version of a product that genuinely solves a user's problem. You build one to test the idea against a real market before spending the whole budget.
- SaaS Software as a Service
- Software delivered through the browser on a subscription, with nothing installed on the customer's side. One application serves many customers at once.
- API Application Programming Interface
- An agreed way for two systems to exchange data. It is what lets a store talk to a courier, or a mobile app talk to your database.
- CI/CD Continuous Integration / Continuous Delivery
- Automation that runs the tests and ships the app to the server every time the code changes. It removes manual file uploads and the mistakes that come with them.
- Core Web Vitals
- Google's three measurable signals for how fast and how stable a page feels. They feed directly into where you rank in search results.
- Headless
- An architecture that separates the content management back end from whatever displays it. The same content then feeds a website, an app and a kiosk.
- PWA Progressive Web App
- A website that installs on a phone like an app and keeps working without a connection. A cheaper alternative to a full native mobile app.
- Staging
- A copy of the application identical to the live one but visible only to us. It is where you review and sign off on changes before any customer sees them.
- Technical debt
- The shortcuts taken in the code to hit a deadline. Not a bad thing in itself — it turns bad when nobody pays it down and every new change costs more than the last.
- Refactoring
- Rebuilding the code without changing anything the user sees. You do it so the next round of features can be added faster and cheaper.
- SLA Service Level Agreement
- A written commitment to a specific response time and uptime. Without one, "urgent outage" means whatever anyone decides it means that day.
- Multi-tenant
- A single application instance serving many independent customers with their data fully separated. The standard approach for SaaS platforms.
What next
Also worth a look
Let’s start
Got a project in mind?
Describe it in a few sentences — I reply within 24 hours with a free quote and a proposed stack.