Your client came in with an idea. I’ll turn it into an MVP.
I run the project from the first conversation to a working version. I talk to your client in Polish or English, work with your designer or without one, on a stack we agree on together.
NDA before the details. I reply the same business day (Polish time, CET).
What it’s costing you today
A client’s great idea has a way of showing up in your busiest week.
- 1The client is waiting to hear back
Your team is deep in another project, and the client wants to know when you’ll start. - 2The idea goes elsewhere
You say no because there’s nobody to put on it, and the client keeps looking. - 3Designs done, nobody building
The designer has wrapped up, and the build is waiting for free hands.
Two ways to work together
- From idea to MVP, with your clientThe client has the idea, you have the client. I run the build from the first conversation to a working version, and fit in with what already works for you: your designer, your milestones, your reporting.
- Client calls in Polish or English
- With your designer or without
- We pick the stack together
- You own the client relationship
- A module on contractA complete module built to your spec, in your repository and your conventions. Learn more →
How an MVP goes
- Step 1
A call with you
You tell me what you’ve already agreed with the client and what’s left to figure out.
- Step 2
A call with the client
With you or on my own, in Polish or English. I keep asking until the idea can be written down.
- Step 3
The plan
MVP scope on one page, acceptance criteria, a date. You and the client sign off.
- Step 4
The build
A clickable version every week. The client sees progress, you see the code.
- Step 5
Handoff
Tests, documentation, deployment. The code is yours.
The module your team never has time for
I build it to your spec, in your repo. PRs go through your review, tasks through your tracker. If I see a better way, I’ll suggest it; the decision stays with you.
- NDA before the details
- Your repo and conventions
- Tests and docs included
How billing works
- A fixed price after the planFor an MVP or a module with a clear scope: one price for the whole thing, set after the brief.
- HourlyWhile the scope is still taking shape. Billed monthly with a timesheet.
- The first callCosts nothing and commits you to nothing.
I give you a number after we talk, once I know what we’re building. The contract is short and covers specific work.
Send me the idea or the module spec, and I’ll send back a plan or questions. Book a call→
When you don’t need me
- 1You’re looking to hire someone permanently onto your team.
- 2The client doesn’t know what they want yet, and doesn’t want to talk about it.
- 3An off-the-shelf service or library would do the job.
Not sure this project should go outside? Let’s talk before the plan. Book a call→
Questions
Will you talk to our client in English?
Yes. Calls, the plan and reports can be in Polish or English.
We already have a designer. How do you fit in?
I work from their designs and within your milestones. If there’s no designer, I build a simple, clean interface myself.
What stack do you build on?
One we agree on together. Yours, if your team will take the code over later.
Who manages the client relationship?
You do. Up front we agree on what my role is in conversations with the client.
Will you sign an NDA?
Yes, before we get into the details.
Who owns the code and the rights?
You or your client, after handoff, as set out in the contract.
Let’s talk
Pick a time. Tell me about your client’s idea or the module; I sign the NDA before the details.
Pick a day
Time zone: Europe/Warsaw
All set
You’re booked
A Google Meet link is on its way to your inbox.
- You’re booked
- I’ll hold the slot for 30 minutes while you pay.