Miha PlohlDeveloper | Sculptor / manituSL
Help with applications built using AI

You built the app.
Now it needs to work.

AI helped you build the first version. Real users are now uncovering bugs, limitations or rising costs.

I help identify what is going wrong and find a practical way forward. You do not need to know the code or technical terminology: show me the app and explain what it should do.

Where are you stuck?

It breaks in production

Login fails, data does not save, the app is slow or a fix breaks something else. I investigate the causes and what needs to change for more reliable operation.

Running costs keep growing

Subscriptions, AI calls and platform usage are becoming too expensive. I review the cost drivers and compare optimisation, alternative services and independent hosting, including ongoing maintenance.

You want to export or leave the AI platform

You built an app with Base44, Lovable or a similar tool and want more control. I review the available code, data, authentication and integrations to identify what can move and what needs replacing.

Keep what is useful.

A working prototype is a valuable start: it shows what you want to build. I first check what can be retained. Sometimes a few fixes are enough; sometimes part of the system needs replacing. A full rebuild is an option when the findings justify it.

I have more than 20 years of production software experience. As lead developer I built Jetpack Workflow from the start to thousands of daily users, and I now develop eternalfriend.io on my own.

Review first.
Then decide.

  1. Send a link, a description of the problem, the platform name and approximate monthly costs. Do not send passwords or user personal data in the initial enquiry.
  2. We agree the scope and price of a technical review. I assess operation, platform dependencies and the main risks.
  3. You receive a recommendation: fixes, a partial migration or a rebuild, with an estimate of implementation and running costs.
  4. You choose the next step. Implementation, verification and any ongoing maintenance are agreed separately.
Base44 / export and migration

Exporting an app from Base44

Built an app in Base44 and want to export it, host it independently or reduce running costs? I help assess what can be transferred from your project and what it needs to run outside the platform.

I first review the export options available for your project, source code and backend connections. Then I check the database, user accounts, files and integrations. Downloading code alone does not guarantee that the whole application will run independently.

The review produces a migration plan with estimates of implementation and running costs. If fixing the current app or moving only part of the system makes more sense, I recommend that option too.

I need help exporting from Base44
Lovable / export and migration

Exporting an app from Lovable

Built an app in Lovable and now need help exporting the code, deploying to another host or continuing development? I review the project and assess what the next step requires.

I check the available code, environment configuration, authentication, data storage and connected services. If the app uses an external backend such as Supabase, I review that dependency separately: moving the frontend alone does not move the data and user accounts.

We compare keeping the existing services, changing hosting and potentially replacing the backend. The goal is a clear plan for reliable operation and manageable running costs.

I need help exporting from Lovable

Common questions

Can you help if I cannot code?

Yes. Start with the problem in your own words and a demonstration of the app. I explain the technical findings and options so you can decide what to do next.

Can you export an app from Base44 or Lovable?

I first check the options for your specific project and access level. Exporting code does not automatically make the database, authentication, files and external services independent. I assess migration scope after reviewing these dependencies.

Will independent hosting be cheaper?

It can be, but savings are not guaranteed. We compare subscriptions, actual usage, migration costs and maintenance. If migration does not make financial sense, optimising the current app may be a better choice.

What does it cost and how soon can we start?

Price and timing depend on access, the condition of the app and the problems involved. We agree a review after your initial description; an implementation estimate follows the findings. Mention if the problem is already affecting users.

Indicative pricing

A small first step.
Clear limits on cost.

Start with a consultation or a limited review. Before any further work, we agree the scope and spending cap. I do not exceed it without your agreement.

Technical consultation · €90

Up to 60 minutes discussing and demonstrating the app, plus a short summary of recommendations. Suitable for understanding a problem, getting guidance or choosing a next step. A fix within the session is not guaranteed.

Initial review · €240

Up to 3 hours of total work, including preparation, investigation of the agreed issue and a summary of findings. You receive a recommendation and an estimate for the next step. This is not a comprehensive security audit or a review of every feature.

Further work · €80/hour

Fixes, optimisation and development within an agreed scope and spending cap. Migration is quoted separately after reviewing the code, data and dependencies.

An initial call of up to 15 minutes to check whether we are a good fit is free and does not include code review. Hosting, subscriptions and third-party services are not included. The proposal states the final amount and any applicable VAT.

Describe the problem and agree a first step
Direct contact

Show me where it gets stuck.

Include a link to the app, the AI platform you used and what is broken or too expensive. If known, include monthly costs, your preferred timing and approximate budget. Do not send passwords or secret keys through the form.

Miha Plohl · Slovenia
info [at] manitu [dot] si

This form does not accept attachments. You can send photographs by email after I reply.

Read as Markdown · llms.txt