You will get your broken AI-built or no-code web app fixed and deployed
Project details
You built something with Lovable, Bolt, Replit, Cursor or v0. It looked finished. Then it will not deploy, or it deploys and breaks the moment a real person uses it.
I fix that. It is most of what I do.
I work in production every day on Laravel, React, TypeScript and Node. Real faults I have found and fixed: a container that built green in CI and then restart looped forever, because the base image shipped no OpenSSL and the database client could not load. A dashboard that built its date window in local time but bucketed it in UTC, silently dropping today's sales. A checkout that answered HTTP 500 for any basket holding an out of stock item, so the customer saw a crash instead of a message.
None of those appeared in a passing test suite. They appeared when somebody ran the thing.
So that is how I work. Reproduce the fault first. Find the actual cause, not the symptom. Fix it, then check the rest of the app still works before handing it back. You get a plain English explanation of what was wrong, not just a commit hash.
If it is a bigger job than the tier you bought, I tell you before I start, not after.
I fix that. It is most of what I do.
I work in production every day on Laravel, React, TypeScript and Node. Real faults I have found and fixed: a container that built green in CI and then restart looped forever, because the base image shipped no OpenSSL and the database client could not load. A dashboard that built its date window in local time but bucketed it in UTC, silently dropping today's sales. A checkout that answered HTTP 500 for any basket holding an out of stock item, so the customer saw a crash instead of a message.
None of those appeared in a passing test suite. They appeared when somebody ran the thing.
So that is how I work. Reproduce the fault first. Find the actual cause, not the symptom. Fix it, then check the rest of the app still works before handing it back. You get a plain English explanation of what was wrong, not just a commit hash.
If it is a bigger job than the tier you bought, I tell you before I start, not after.
Programming Languages
PHP, JavaScript, TypeScriptCoding Expertise
Cross Browser & Device Compatibility, Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$45
|
Standard
$120
|
Advanced
$275
|
|---|---|---|---|
| Delivery Time | 2 days | 3 days | 5 days |
Number of Revisions | 1 | 2 | 3 |
Bug Investigation | |||
Fix Documentation | - | ||
Detailed Code Comments | - | - |
Frequently asked questions
About Rakibul Hasan
AI Integration & Automation Engineer | Full Stack | Rescue Work
Dhaka, Bangladesh - 6:37 pm local time
A lot of what I am hired for now starts the same way: someone built an app with an AI builder or a no-code tool, it demos beautifully, and then it breaks the moment real users touch it. Broken auth. Data that does not sync. Deploys that work in preview and fail live. I take those over, find the actual root cause, and ship them properly. I do not start by telling you to rebuild it.
I also build from scratch when that is genuinely the cheaper answer.
WHAT I DO
- Rescue and harden AI-generated or inherited apps (Lovable, Bolt, Replit, Base44, v0, no-code exports, abandoned codebases)
- Migrate apps off vendor hosting onto infrastructure you own
- AI assistants that answer from your own data, cite sources, say "I do not know", and hand off to a human
- Business process automation (n8n, webhooks, API integrations)
- Full stack web applications and REST APIs
- Production debugging, deployment, security hardening
WHY CLIENTS KEEP ME
I find the bugs that testing does not. That is not a slogan, it is the actual pattern of my work:
- A service that passed every test in CI but restart-looped in production, because the base image shipped without the SSL library its database driver needed. The build was green. The container had never once booted.
- A sales dashboard that quietly dropped the current day's revenue, because it built its date window in one timezone and grouped by another.
- A courier integration that declared every parcel as 0.5 kg. One real order weighed 12.25 kg. Nobody noticed, because nothing errored.
- A checkout that returned a 500 server error whenever a basket contained something out of stock, so customers saw a crash instead of a message.
Every one of those looked fine until someone actually ran the thing. That is what I do before I hand anything over.
HOW I WORK
I ask questions before I write code. If I think your plan has a problem, I will say so and tell you why. If a smaller and cheaper fix solves it, I will recommend that instead of the bigger job.
I write documentation and hand over systems you can run without me. I would rather have a client who comes back than one who is stuck with me.
I work fixed-price wherever possible. I am fast, and hourly billing punishes that. You get a number and a date up front.
STACK
AI: Claude API, OpenAI API, RAG, embeddings, pgvector, prompt engineering, agents, MCP
Backend: Laravel, PHP, Node.js, TypeScript, PostgreSQL, MySQL, Redis
Frontend: React, Next.js, Vue, Inertia, Tailwind
Automation: n8n, webhooks, REST APIs, third-party integrations
Infra: Docker, Linux VPS, nginx, Traefik, GitHub Actions, CI/CD, Supabase
I am in Bangladesh (GMT+6), which overlaps the UK, Europe, the Middle East and Australia. Flexible for calls.
Tell me what is broken, or what you are trying to build. I will tell you honestly whether I am the right person for it.
Steps for completing your project
After purchasing the project, send requirements so Rakibul Hasan can start the project.
Delivery time starts when Rakibul Hasan receives requirements from you.
Rakibul Hasan works on your project following the steps below.
Revisions may occur after the delivery date.
Reproduce the fault on my own machine
I run your app myself and make the problem happen. If I cannot reproduce it, I tell you on day one rather than guessing at a fix.
Find the real cause, not the symptom
I trace it to the actual line. You get a plain English explanation of what was wrong and why it happened, so the same thing does not surprise you again.