Kenlore · engineering for products without an engineer

Your product is live. Who do you call when it breaks?

A freelancer, an agency, a co-founder, an AI builder: whoever wrote it, you now need someone who can read the code, tells you the price before touching it, and answers when you write. That is Kenlore. Connect your repo to Kenlore, write what is broken in plain words, and see the price before anyone touches a line. An experienced engineer takes ownership of your project, plans every task, does it and checks it, and a team you can always reach stays with you. Not another AI. You pay at the end of the month, only for what you approved.

Start with $300 on us →See how it works
$300
We are sure this fixes what you are stuck on. So sure that your first $300 of work is on us.Sign up, connect your app, and spend it on real requests for one week. See it work before you spend a dollar of your own. Your balance is in dollars, every charge is in dollars, always.
We don’t disappear: a named engineer and a team you can reachEverything stays yours: repo, accounts, domain, recordThe price before the work, never hours
attempt 14 · password reset
your AI builderTuesday, 11:40 pm
80% complete · since March
builder credits left1,500
Last 20why this offer has that name
80%

Built in a weekend. Screens, flows, a database, a demo that made your co-founder gasp. This part, AI does brilliantly, and you should keep using it for this part.

20%

Logging in. Getting paid. Not getting hacked. Staying online. The part that never ends.

You did nothing wrong. The last 20% is not more prompting. It is a short list of boring, testable tasks that need a person who can read the code and answers when you write. That is what Last 20 is: the offer on Kenlore for founders who are almost there.
You know this moment

Six things people say the week they call. Ranked by how often they say them.

We read 458 public posts by owners whose developer, agency or co-founder was gone, 40 client reviews of freelance platforms and agencies, and 30 Italian owners’ stories. Then 5,549 more from people who built with AI. These are the six that repeat.

01 · stopped answering · 21%, and 46% when a freelancer built it
“He removed all my access to the websites I built. I need his cooperation to switch my domain over, which he verbally said he would provide.”
UnderneathOne person held the repo, the hosting login and the domain. When they moved on, or stopped picking up, your product stayed where they left it.
What we doAn engineer with a name takes ownership of your project, and a delivery manager you can always reach stays with you. If your engineer changes, the next one reads the project record instead of asking you. Nobody here is a single point of failure.
02 · the price that never stops · 32%, and 60% when an agency built it
“Every weekly report showed 160 hours billed. But the feature backlog wasn’t moving.”
UnderneathHourly retainers and open-ended quotes pay for time, not results: 500 hours sold, 1,000 billed; €3,000 and nine months to add a logo to a report.
What we doYou write the request, you see the scope, what “done” means and the price before anything starts, and you approve it. The monthly invoice lists what you asked, what was done, what it cost. Nothing else. No hours, ever.
03 · weeks for a small change · 26%
“Every time a change was planned, it took weeks and my multiple reminders to do what was planned to be done.”
UnderneathYour fix is someone else’s side project. Three weeks for a price-list change, months of “almost done”, a site that keeps going offline after the job was marked complete.
What we doWrite it in plain words, the way you would tell a friend. An engineer replies within the first working day, and the work shows up on a test environment you can check before it goes to your users.
04 · nobody knows how it works · 20%, and 41% when the developer left an in-house product
“The next developer quoted four weeks just to understand it. It works, but nobody knows how.”
Underneath85,000 lines with no documentation, a 23-line README as the whole handover, a comment that says “it works, I don’t know why, don’t touch it”. The knowledge lived in one head and left with it.
What we doWe read the whole codebase once, write the runbook (where the code lives, how it deploys, who holds which key), and record every decision and its reason in your Kenlore project record. It survives any change of people, including us.
05 · it was never really yours · 17%, and 39% when a co-founder or employee built it
“He owns the website along with the user database, which is a major concern.”
UnderneathDomain on the developer’s personal email, server in the agency’s account, source code held until the last invoice is paid. You paid for it; that did not make it yours.
What we doEvery account moves into your name: repo, hosting, domain, database. We are collaborators you can remove in one click. We never connect to your production. The project record leaves with you if you go.
06 · “fixed” again · when an AI builder wrote it
“Each time, it tells me ‘I finally understand what the problem is!’ and claims to have fixed it. Each time, it does not work.”
UnderneathThe model cannot run your app, so it guesses. Each guess touches something you never asked it to touch, and the credits go with it. Named by 32% of 5,549 AI-builder users.
What we doA human reads the whole codebase once, finds the root, not the symptom, and fixes it. Password reset gets one test that proves it works. This door has its own name on Kenlore: Last 20.

Shares: percentage of relevant public posts naming each problem (458 owners with a non-AI origin, 14 founder and small-business communities, 2025–2026; the AI figure from 5,549 records). Quotes are verbatim from clients, lightly trimmed. Per-origin figures are directional.

46%of owners whose product was built by a freelancer say the freelancer stopped answering
60%of owners whose product was built by an agency name cost surprises or hours without results
44%of those whose developer vanished are looking for one reliable person, ongoing. Not an agency: 2%
Who comes to Kenlore

Four ways to end up with a product and no one to call. Each has its own first complaint.

The code came from different places and the first thing owners say differs. The request, the price and the person who answers work the same way for all of them.

You built it with an AI builder

  • First complaint: “I’m burning credits trying to fix one thing” (32%) and “it broke something I never touched” (28%)
  • The last 20% never arrives: auth, payments, security, hosting you own
  • The builder’s support does not answer; you are the founder, the support desk and the only engineer

This is the offer we call Last 20: we read the code, finish the last 20%, and stay.

A freelancer built it, and stopped answering

  • First complaint: “disappeared”, “stopped responding” (46%), then the price (38%) and the wait (34%)
  • Domain, hosting and repo were in their name; you find out when something breaks
  • “4th developer on this site. The other two gave up.”

We take ownership, move every account into your name, and every decision from now on is recorded so this cannot happen twice.

An agency built it, and the invoices kept coming

  • First complaint: the price (60%), then weeks for a change (40%), then the agency going quiet (26%)
  • “500 hours sold, 1,000 billed, still unfinished”; “€3,000 and nine months to add a logo”
  • You need changes at a price you know before you say yes, and a person who replies

Per request, priced first, approved by you. One engineer who knows your codebase, with a monthly cap you set.

Your developer or co-founder left, and the knowledge left with them

  • First complaint: they are gone (50%), the knowledge is gone (44%), the access is gone (39%)
  • In-house products with no developer left: “nobody knows how it works” (41%), “nobody dares touch it” (33%), “we can’t afford a hire” (33%)
  • The portal, the gestionale, the back office that replaced the spreadsheet, and breaks on the day you need it

We read the whole codebase once, write the runbook, and keep the product moving without a hire or a retainer.

How it works

Write it. See the price. Say yes. Done.

No sales call, no scoping workshop, no hourly rate. Four steps, and the price always comes before the work.

1

Connect your repo

Sign in to Kenlore with GitHub and pick one repository. We read the code, set up a working copy of your app on our side, and an experienced engineer takes ownership of your project and says hello. Your production is never touched.

2

Write the request in plain words

“Password reset doesn’t send the email.” Not a ticket, not a spec. The way you would tell a friend.

3

See the price before anything happens

You get the scope in one sentence, what “done” means, and a price range. A one-line fix is a few dollars. A broken payment flow is around a hundred. Rebuilding half a system is hundreds. Nothing starts until you click confirm.

4

Get it working, pay at the end of the month

Your engineer does the work, checks it, and shows it to you on a test environment. You check it, then roll it out to your users. Your invoice arrives at the end of the month: what you asked, what was done, what it cost.

Kenlore · acme-applive preview
your request
Password reset doesn’t send the email.
estimate · before any work
Fix the reset email. Done means: a reset link arrives and works, verified in live mode.
$60 to $90approve to start
your engineer
The token was generated but never saved. Fixing the flow and adding one test that proves it.
working…
your balance$300.00
Your team

Not another AI. People who look after your project.

You have had enough of a chat window that says “fixed”. On Kenlore your app gets an experienced engineer who owns it, and a team you can reach whenever something is wrong.

ENG
Your engineer

Experienced, and in charge of your project

Not a queue and not a bot. One senior engineer reads your whole codebase, plans every task, does the work, tests it and stays on your project. Nothing changes in your app without a person deciding it and checking it.

DM
Your delivery manager

Always within reach

Write whenever something is wrong or unclear, and a human answers. Your delivery manager keeps your requests moving, tells you what is happening and when, and makes sure nothing waits in silence.

AI
Our AI tools

Used by engineers, never left alone

We use the same AI tools you do, and they make us faster. The difference is who is holding them: an engineer who can read the result, sees what would break, and takes responsibility for every change.

The seventh thing founders tell us

“When the contract ended, all the context walked out the door with them.”

A SaaS co-founder, March 2026. The freelancer who built it is gone, the deploy password went with them, and the new developer quoted four weeks just to understand the code. We built the fix into how we work.

Everything your team does on your app, every request, decision and deploy, is written into your Kenlore project record: what was asked, what was done, why it was done that way. If your engineer changes, the next one reads the record instead of asking you to explain your product for the third time. If you leave, the whole record leaves with you.

Scope before workEvery task has a written “done means” you approve before anyone touches code.
Decisions with reasonsWhy we chose this, what we rejected, what it would break. Searchable.
Yours to exportThe whole record leaves with you, including to the engineer you eventually hire.
Kenlore · project record · acme-applive
Mon 09:12
request

Customers on annual plans see “trial expired” after renewal.

Mon 09:20
estimate approved

Fix renewal webhook. Done means: renewed accounts stay active, verified in live mode. $120 to $180.

Tue 15:05
decision

Kept the existing payment product IDs instead of migrating; migration would log out active users.

Wed 11:30
pr #142

Signed webhook handler, idempotent renewal, 6 tests on the payments path.

Wed 17:48
on your test environment

Verified with a real annual renewal. You roll it out. Alert on failed webhooks set to your phone.

end of month
monthly invoice

1 request · $150 · balance after: $150

3 wks later
engineer changed

Nothing lost. New engineer onboarded from the record in an afternoon. You were not asked a single question.

Why founders stay

Four fears founders admit to. Each one has an answer.

We are not a better chat window. We are the part the chat window cannot be: an experienced engineer in charge, a team that answers, a price you see first, and a memory that stays.

1

“Cheap ones disappear. Expensive ones bill hours.”

Nobody bills hours here. Every request has a price you see and approve before it starts, and a spending cap you set for the month. One named engineer stays on your project, plus a delivery manager you can write to. When we are full, we say so.

2

“I’ll become dependent.”

You keep building with your AI tools in the same repo. We review and merge, catch what would break payments or login, and explain what we changed and why. You understand more of your product after we arrive, not less.

3

“Nobody answers.”

When something is wrong, you write to a human and a human replies, by name. That is the whole point, and the thing no builder gives you. Everything they learn about your app is written into your project record, so nothing is lost when people change.

4

“Never give a stranger your repo.”

Correct. The code stays in your own repository from day one. We work in a copy and hand you the result. Every account in your name, production never touched, and you can remove us in one click.

Pricing

$300 to start. Then only what you approve.

No subscription, no package, no hourly rate. Your balance is in dollars. Every request has a price you see before it starts.

Your first week
$300of engineering, on us

We are confident this solves your problem, so the first $300 of work is our risk, not yours. Sign in to Kenlore with GitHub and the $300 is yours for one week: connect your app, meet the engineer who will look after it, get the first real things fixed. No card needed to start.

  • Shown in dollars, never in tokens or credits
  • Every charge in dollars, before it starts
  • Unused balance expires after seven days
Every request after that
Priced firstyou approve, then we start

A range before the work, a fixed figure on the invoice, never above the top of the range. Small things cost a few dollars. Big things cost what they cost, and you know it before saying yes.

  • “Done means” written down for every task
  • Bigger jobs get a fixed quote before we start
How you pay
Monthlyone invoice, end of month

You pay for what was done that month, by card. Set a spending cap and we warn you before any request would cross it.

  • Every line: what you asked, what was done, what it cost
  • Pause or leave any month
!
Plain talk about the invoice. If a monthly invoice goes unpaid, we pause the work until it is settled, and we tell you before we do. No surprise charges, no fine print. Your project record stays yours either way.
Fit

Built for anyone with a live product and no engineer to call.

A founder, a small team, a business owner. Whoever built it, people use it, and now it needs someone who can read it.

You will feel at home if

  • Your web app is live, or launching soon, and real people use it or will
  • There is no engineer on your team, or the one who wrote it is gone: AI builder, freelancer, agency, it does not matter
  • You would rather delegate the engineering than learn it or hire for it right now
  • Your first question is “what will this cost me” and you want the answer before, not after

What we are built for

  • Web apps on a standard React and TypeScript front end with a Postgres database, which is exactly what the popular builders generate
  • Code on GitHub. If yours lives inside a closed builder or on a freelancer’s laptop, tell us and we will walk you through getting it out
  • Auth, payments, security, hosting you own, backups, monitoring, and the everyday fixes in between

Something else on your mind, a mobile app, a data pipeline, a bot? Write to us anyway. If it is not ours, we will say so and point you to who does it well.

Questions

The ones everyone asks.

What exactly happens after I sign in?+

You land in Kenlore, our platform, and pick one GitHub repository. We read the code and set up a working copy of your app on our side. An engineer writes to you, by name, within the first working day. Then you write your first request in plain words and see what it would cost.

How can you know the price before you start?+

We can’t know it to the cent, and we don’t pretend to. You get a range and a written “done means”. The invoice shows the actual figure inside that range, never above it. If a task turns out bigger than we thought, we stop and tell you before spending more.

Is the $300 in credits or tokens?+

Neither. It is $300. Your balance is in dollars, every charge is in dollars, and the invoice is in dollars. No tokens, no points, no conversion rate to guess at.

How does this compare to a freelancer or an agency?+

Founders report $25 to $1,400 a month in builder credits for the same bug surviving dozens of “fixed” messages, $16 to $35 an hour for contractors who disappear on day 14, and $10,000 or more a month for agency retainers. Here you pay per request, you see the price first, and the same engineer stays on your code.

Do you bill hours?+

Never. You approve a price per request. How long it takes us is our problem, not yours.

Can I set a limit on what I spend?+

Yes, and we recommend it. Set a monthly cap in your account. We warn you before any request would cross it, and nothing starts without your yes.

Can I keep building with my AI tools myself?+

Yes, in the same repo. We review and merge your changes, catch what would break payments or auth, and explain what we changed and why so you stay in control of your own product.

Who actually does the work? Is it an AI?+

An experienced engineer attached to your project, working from your project record. They plan each task, do it, test it and take responsibility for it. We use AI tools the way any good engineer does, but a person controls every change. You also have a delivery manager you can write to at any time. Both are people, and both answer.

Do you touch my production?+

No. We work in a copy of your app on our side and show you the result on a test environment. You roll it out to your users when you are happy with it. Your accounts stay in your name.

What happens to the project record if I leave?+

You export it. Requests, decisions, deployment history, the runbook. It is your project’s memory and it goes where you go, including to the engineer you eventually hire. We help with that hire too, when you are ready.

My builder now scans for security issues. Why would I need you?+

Keep the scan on; it is free and it catches the obvious. Two months after the biggest platform added auto-fix, a public scan of 30,998 live apps still found 57% of reachable backends open to anonymous reads. Scanners find patterns. They do not know that your “admin” table is the one with your customers’ invoices in it, and they do not answer when a customer is locked out.

Who are you, and what is Kenlore?+

WWG is a software company based in Milan. Kenlore is our platform: the place where your code, your requests and your project record live, with named engineers behind it. Last 20 is the offer on Kenlore for founders who already have a product and users. You meet your engineer before you spend a dollar.

Start here

Get someone to call when it breaks.
The first $300 of work is on us.

Sign in to Kenlore with GitHub, connect one repo, write what is broken. See the price. Say yes. An experienced engineer and a team that stays in touch take it from there.

Start with $300 on us →Or just email us

Valid for one week · shown in dollars · no card to start

K

We built Kenlore because we kept meeting the same person. A founder, a two-person SaaS, a business owner with a portal nobody would touch. Real customers, a product that was almost there, and no one left who could read the code. Nobody needed a bigger agency. They needed an experienced engineer who would read the code, say what it costs, and then stay, with a team behind them that answers.

The Kenlore team, WWG · Milan