The engineering your agency sells, built by one person you can reach
Broken funnels, integrations that drop data, booking systems, client dashboards. I work under your name, quote a fixed price before I start, and answer the same working day.
No hourly billing. No retainer to start. No contract.
Start with one fix
You have no reason to trust a stranger with a client's site, so don't. Send me the smallest broken thing you have — the form that fails on mobile, the integration that drops every tenth lead, the page nobody can make fast. You get a fixed price and a date before I touch anything.
Bigger work is quoted per job once we have done one. That order is deliberate: talking price on a project with someone you have never worked with is a guess for both of us.
Book a 15-min callHow I work, in full
- White-label. Your client never hears my name.
- Fixed price agreed before the work starts.
- Your NDA signed before anything is sent.
- Code in your repository, yours from the first commit.
- Replies within hours on a working day, not days.
- If a job grows, you hear it before the work, not on the invoice.
What I build
The technical half of what an agency sells, and the parts a template shop tends to push back on.
Funnels and landing pages that stop converting
A form that fails silently on iOS, a page that takes eleven seconds on a phone, a button that does nothing below 400px wide. The ad spend keeps running either way, which is why nobody catches it.
Integrations between things that were never meant to talk
CRM to booking tool, booking tool to invoicing, webhooks that drop payloads at 2am and nobody notices until a client counts leads.
Booking, scheduling and payment systems
Availability, deposits, reminders, no-shows, refunds. I have built five of these end to end and run all five in production.
Client-facing dashboards and admin panels
The screen your client logs into to change their own content, see their own numbers, and stop emailing you about a typo.
Speed and Core Web Vitals, measured not guessed
Before and after numbers on a throttled phone, on the pages that actually take the traffic.
Builds that stalled
A half-finished project from a developer who went quiet. I read the code first and tell you honestly whether it is worth finishing or restarting.
How it works
Three steps, and none of them is a discovery call you have to sit through to get a number.
You send the job
A link, a screenshot, or two sentences. I come back with a fixed price and a date before I start. No discovery call to get a number, no hourly meter running.
I stay invisible
Everything is white-label. Your client hears your name, sees your branding and talks to you. I do not contact them, and I am happy to sign your NDA before you send anything.
You get an answer the same working day
I am in Valencia, Spain, so my afternoon is your morning on the East Coast. The thing that costs agencies clients is not price, it is a partner who goes quiet for two days. That is the part I am selling.
Shipped and running
Five products for five industries, all live, all built and operated by one person. That is the portfolio: not screenshots, software that has to keep working on Monday morning.
Quotes, menus and event scheduling for catering companies.
Direct booking and guest messaging for short-stay rentals.
Seats, departures and payments for tour operators.
Lesson scheduling and instructor hours for driving schools.
Terms, classes and attendance for skills schools.
A full CV, including the years before these, is at lazarkocic.dev/cv.
Questions
The ones worth asking before you hand a client's site to someone you just met.
Why does the first job have a price on it and the rest don't?
Because you have no reason to trust me yet. A fixed price on a small job means you can find out how I work for the cost of a rounding error instead of a decision. Once we have done one or two, quoting a project is a normal conversation.
Do I have to replace my current developer?
No, and I would not suggest it. Most agencies already have someone for template work, and they are cheaper at it than I will ever be. Send me the thing they keep pushing back on — the integration, the part that breaks, the build nobody wants to touch.
Is it really white-label?
Yes. I work under your name, in your repo or mine, with your client never on a call with me unless you want me there. NDA before anything is sent is fine and normal.
Who owns the code?
You do, from the first commit. It ships to your repository or your hosting, with a written handover, so nothing about your client's site depends on me still being around.
What don't you do?
Logo and brand design from scratch, ad buying, SEO content, and anything that needs a team of six. I am one engineer. If a job is outside that, I say so on the first email rather than after you have promised it to a client.
Do you bill hourly?
No. Fixed price per job, agreed before the work starts. If a job turns out bigger than it looked, I tell you before I do the extra work and you decide — it is never on the invoice as a surprise.
How do I know the work is any good?
Five products below, all live, all built and run by one person. Read the code quality question the other way round: the first job costs you a few hundred dollars and answers it better than any portfolio can.
Who am I actually talking to?
Lazar Kocic, a software engineer who has built web products for more than a decade. One person, so the one who answers your email is the one writing the code.
Fifteen minutes, no pitch
Tell me what keeps landing on your plate that you would rather hand off. If I am not the right person for it, I will say so on the call and we both keep the afternoon.
Book a 15-min call