Skip to main content

A free code health check for your AI-built app

You have an app built with an AI tool such as Lovable, Bolt, Replit, v0, Cursor, Claude Code, Codex, GitHub Copilot or Windsurf, and people want to use it. We read the code, explain in plain English what is likely to fail as more people use it, and quote a fixed price to fix it. Your first health check is free.

Who it is for

Founders, hobbyists and small businesses whose app was built mostly with AI coding tools. It might be a side project that has started to get users, or the product your business now runs on. You may not write code yourself, or you may write some and know the AI wrote the rest. Either way you need to know what is underneath before more people depend on it.

Signs it is time

  • It slows down as more people use it.
  • You are not sure who can see whose data.
  • Keys and passwords sit in the code, or in the browser.
  • Every change breaks something else, and nothing tells you what.
  • You deploy by hand and cannot easily undo a bad release.
  • Your hosting or AI bill is growing faster than your users.
  • An investor, a customer or an app store reviewer has asked a question you could not answer.

What we do

  • Security

    We check sign-in, check permissions on the server for every request, move secrets out of the code, validate what users send, and limit how often anyone can try your sign-in or call your API.

  • Scaling

    We look at how the app uses its database, add the indexes and limits it is missing, and move slow work such as emails and imports into background jobs so one busy user cannot hold up everyone else.

  • Speed

    We measure where the time goes and fix the slowest parts first. In generated code the usual causes are a loop inside a loop and the same data fetched over and over, and both get slower as your data grows. We rewrite those parts so the time they take grows in line with the amount of data.

  • Caching

    We cache data that rarely changes, so the app makes fewer database and API calls. That makes pages load sooner and can lower the hosting bill.

  • Containers

    We package the app in a container so it behaves the same on a laptop, in testing and in production, and so you can move to another host later without rebuilding it.

  • Shipping

    Automated checks run before every deploy, changes go to a staging copy first, and a bad release can be rolled back to the last working version. App Store and Google Play builds and submission are available as extra days.

  • Monitoring

    We set up error reporting and health checks in your own accounts, so an alert tells you when something fails.

Who does the work

Luke built Bog Standard, live on iPhone and Android, and runs it himself: the mobile app, an API shipped in containers to Azure through an automated pipeline, a cache in front of the database, scheduled jobs, and content safety on everything the public posts. Every area on this page is one he looks after on his own product, and you can download the app to see it before you contact us.

Luke does the health check and the fixes himself, so your project is never handed to someone else partway through.

We harden the code the tools wrote and keep the parts that work. If a rebuild would cost you less, the health check says so.

From request to handover

  1. 1

    Request a health check

    Email enquiries@gimzware.ai with a line about your app and what you would like fixed.

  2. 2

    Free health check

    You give us read-only access to the code. We send you a written report in plain English that ranks each problem by how much it matters and prices the fix. Your first one is free, and the report is yours to keep whether or not you go ahead.

  3. 3

    A fixed quote

    We send a written quote with the scope, price and start date fixed before any work starts. You choose which problems to fix.

  4. 4

    Fix and ship

    We work in your repository in small changes, each with a note explaining it, then deploy with you to a staging copy first so any release can be rolled back.

  5. 5

    Handover

    We walk you through what changed and give you a short document on running the app. Care is optional.

Prices

Every project is quoted to its size. These are starting prices, and the price you pay is fixed in writing before work starts. No VAT to add.

  • Health check: free for your first app, then from £295

    A written report on security, speed, scaling and releases, ranked by risk, with a fixed quote for the fixes. The free health check covers one app per person: one repository of up to about 25,000 lines of code.

  • Launch ready: from £1,950

    Fixes the problems that stop you taking on real users: sign-in and permissions, secrets out of the code, server-side checks on what users send, automated tests on the paths your app depends on, a deploy pipeline with staging and rollback, and error reporting.

  • Scale ready: from £4,500

    Everything in Launch ready, plus the work that keeps the app quick as it grows: database and query fixes, caching, background jobs, the slow code paths rewritten, and the app packaged in containers.

  • Extra days: £450 a day

    For work beyond the agreed scope, such as app store builds and submission, only when you ask for it and agree the days in writing first.

  • Care: from £149 a month

    Dependency and security updates, a monthly look at your error reports, and up to 2 hours of fixes each month. 3-month minimum, then cancel any time with a month's notice.

Tell us about your app

Health check requests open soon. Until then, email enquiries@gimzware.ai with a line about your app and we will reply personally.

Questions

  • Is the first health check really free?

    Yes. Your first health check is free for one app: one repository of up to about 25,000 lines of code. There is no obligation to go ahead, and the report is yours to keep. Further health checks cost from £295.

  • Why are prices "from"?

    The work depends on the size of the app. The health check measures it, and the quote fixes the price before any work starts.

  • Do I have to rebuild from scratch?

    Not unless the health check shows it would cost you less than the fixes, and then it shows why. We start from keeping what works and fixing what is weak.

  • Will you keep my idea and my code confidential?

    Yes. We do not sell or reuse your code or your idea, and we do not discuss your project with anyone outside GIMZWARE. The only exceptions are the services we name to you in writing before work starts, such as where your code is hosted, and anything the law requires. The same promise is in the contract.

  • Who owns the code?

    You do. The work happens in your repository, under your accounts, and what we write is yours.

  • Is this a penetration test?

    No. A penetration test is a separate specialist service in which testers attack the running system, and we do not offer one. We read the code, fix what we find and tell you what we have not fixed. We will not tell you an app is secure, because nobody can truthfully promise that about any app.

  • Which tools and stacks do you work with?

    Any AI coding tool is fine, including Claude Code, Codex and Cursor, because we work from the code it produced. We work in TypeScript, React, Next.js, React Native and Expo, C# and .NET, and Python, and we host on Azure. If your app is built on something else, we tell you before the health check and do not charge you.

  • Do you need access to my users' data?

    Not to check the code. If a fix touches live data, we agree how it is handled, in writing, before we start.

  • How long will it take?

    It depends on the size, and the quote gives you a start date and a finish date. GIMZWARE is one engineer, so we take on only a few projects at a time and do each one properly.

  • Can I keep building with AI tools afterwards?

    Yes. We add tests and checks that catch it when a generated change breaks something, so you can keep using the tools with less risk.

  • Do I have to sign up for Care?

    No. The handover is the end of the work unless you ask for more.

  • Where are you based?

    Newcastle upon Tyne. We work remotely with people anywhere in the UK, and meet in person across the North East where it helps.

Talk to Luke

Tell us about your app and what you would like fixed. Luke reads every request and replies personally.