Operator Insights

Reported by others3

1. 

   Olga AlekseevaGrowth hacking expertKanbanchi

   Bootstrapped 25-person SaaS company. Internal time, salary, leave, and contracts system.

   Kanbanchi blog, published Aug 1, 2026Read the write-up (opens Kanbanchi blog in a new tab)

   Observation

   Kanbanchi's whole team runs its time, pay, and leave system on a Lovable app built without hand-written code.

   Takeaway

   Split the tool into a supervised zone for pay, customer data, and security, with developer review and human checks, and an experimental zone where builders move fast. Budget credits from real daily use.

   What happened

   Kanbanchi replaced a legacy system with an internal Hub built in Lovable from written specifications, with no code written by hand, and the whole team has used it every day since March. Professional developers reviewed the sensitive parts and found security issues, which the team fixed. Non-standard pay calculations still misfire, and a payment-request button once broke and was fixed within hours. The in-app bug tracker shows 36 reports, 25 fixed and 6 marked won't fix. About two hours of building a day can run to roughly €600 a month in credit top-ups.

   • Public organization write-up
   • Team metric reported
   • Credit cost reported in euros

   Deployment details

   Bootstrapped 25-person SaaS company. Internal time, salary, leave, and contracts system.

   • Public organization write-up
   • Team metric reported
   • Credit cost reported in euros

   Team

   The whole company uses the tool daily

   Duration

   Built in February 2026; in daily use from March through the August 2026 write-up

   Workload

   Time tracking, salaries, leave, days off, contracts, and payment requests

   Measurement

   Bug reports logged in the tool and how many were fixed; monthly credit top-ups in euros

1. KnakMay 7, 2026Knak blogKnak's Director of Engineering replaced Figma and Lovable handoffs with designers prototyping in the codebase.

   

   Jack SteeleDirector of EngineeringKnak

   Design and development teams at an enterprise marketing platform. Six-week developer tiger team. Prototyping moved into the production repository.

   Knak blog, published May 7, 2026Read the write-up (opens Knak blog in a new tab)

   Observation

   Knak's Director of Engineering replaced Figma and Lovable handoffs with designers prototyping in the codebase.

   Takeaway

   Where a mature codebase and design system exist, a Lovable prototype is one more artifact to translate. Test whether prototyping on the real components removes the handoff.

   What happened

   Knak's designers worked out layouts in Figma and interactions in Lovable, and each handoff to developers turned up issues that went back to design, leaving a trail of artifacts across tools. A developer tiger team spent six weeks making the production repository a safe place for designers to prototype with Claude Code on real components. Knak replaced the Figma and Lovable handoffs with one git branch. One front-end developer said working from a handoff branch cut their time to production roughly in half.

   • Public engineering write-up
   • Individual estimate with no team metric
   • Lovable dropped from the workflow

   Deployment details

   Design and development teams at an enterprise marketing platform. Six-week developer tiger team. Prototyping moved into the production repository.

   • Public engineering write-up
   • Individual estimate with no team metric
   • Lovable dropped from the workflow

   Team

   Knak designers and developers, with a developer tiger team; no headcount given

   Duration

   Six-week tiger team before designers moved to the new workflow

   Workload

   Feature design and interaction prototypes

   Measurement

   One developer's estimate: time to production roughly halved with the new workflow

2. madewithloveMay 14, 2026madewithlove blogA CTO in residence kept a geologist's Lovable tool and fenced it in with Git, written rules, and CI.

   

   Brenden CambierCTO in residence for a clientmadewithlove

   Client that standardizes geological datasets. Tool built by the lead geologist for students processing data. Engineering team owns the ETL pipelines.

   madewithlove blog, published May 14, 2026Read the write-up (opens madewithlove blog in a new tab)

   Observation

   A CTO in residence kept a geologist's Lovable tool and fenced it in with Git, written rules, and CI.

   Takeaway

   Keep the builder's speed and make the boundaries reviewable, with rules in the repository, CI that enforces them, and engineers owning infrastructure and production.

   What happened

   The client's lead geologist built an internal tool in Lovable that walked students through uploading, processing, annotating, and exporting datasets. The process became clearer, errors dropped, and productivity went up. The tool had also rebuilt parts of the engineering team's ETL logic in Supabase functions. Cambier connected GitHub sync and added a LOVABLE.md file that puts infrastructure, CI/CD, and the shared API client off limits, and made CI block changes that touch them. Cambier also set up local development for engineers working in Cursor or Claude Code and moved the front end off Lovable hosting.

   • Public engineering write-up
   • No team metrics reported
   • Qualitative outcomes only

   Deployment details

   Client that standardizes geological datasets. Tool built by the lead geologist for students processing data. Engineering team owns the ETL pipelines.

   • Public engineering write-up
   • No team metrics reported
   • Qualitative outcomes only

   Team

   Lead geologist, students processing datasets, and an engineering team; no headcount given

   Workload

   Dataset upload, processing, map annotation, and standardized export

   Product version

   Lovable with GitHub sync, Knowledge settings, and a Supabase backend