Small jobs welcome
Something in your app is broken. Let us fix that one thing.
Not a project, and not a call about your roadmap. One named problem in your Lovable, Bolt, v0 or Cursor app — the login loop, the empty list, the key in the bundle, the payment that unlocks nothing. Each page below tells you what is actually causing it, whether you hire us or not.
Already a client? Raise it in Golux Club instead and it enters the queue with an SLA attached.
- First step
- A short call, or a written description if you would rather not talk yet
- Who you speak to
- The engineer who would do the work. No account manager, no sales call.
- Turnaround
- Most single problems are resolved within 48 hours of getting access
- Cost
- Quoted after we have seen it — scope varies, and guessing helps neither of us
How to get this fixed
Already a client? Raise it as a ticket in Golux Club and it enters the queue with an SLA attached.
What we fix
Find your symptom
These eight are what we see most often. Each page says what is actually going wrong, how to confirm it yourself in two minutes, and what we would do. If yours is not here, describe it anyway.
- “I can log in, but every list is empty and there is no error.”The sign-in works. The dashboard loads.Login works, no data shows
- “There is a secret key in my JavaScript bundle.”Our free audit found it, or you pressed F12 and searched for `sk_live`. Either way: rotating the key is the first ten minutes, not the fix.A secret key is in my bundle
- “Signing in bounces me back to the login page, or a refresh logs me out.”You sign in, the dashboard flashes, and you are back at the login screen. Or everything is fine until someone refreshes.Login loops or logs me straight out
- “People pay and the app does not give them what they paid for.”Stripe shows a successful payment. The customer emails you because nothing changed.Payment succeeds, access does not
- “My app is still on yourapp.lovable.app and I want my own domain.”Every bookmark, every link you have shared, every search result and every password-manager entry points at a hostname that belongs to your builder. Moving is not hard, but it breaks four things at once if you only change the DNS — and the four are exactly the ones nobody checks until a customer cannot log in.Move it to my own domain
- “The deploy fails, or it works in preview and breaks in production.”Or the build has been red for two days and the error means nothing to you. Both are the same category of problem: something is different between the place the code was written and the place it runs, and nobody wrote down what.The build or deploy is failing
- “It was fast with ten rows and it is unusable with ten thousand.”Nothing broke. The app just got slower every week until someone complained, and now a page that used to load takes eight seconds or times out.It got slow
- “If the database disappeared tomorrow, I do not know what I would do.”Most founders we talk to have a backup setting switched on somewhere and have never tried to use it. That is not a backup, it is a hope.I have no real backups
Where this sits
Start small. Nobody has to buy a project to find out whether we are any good.
Most agencies want the big engagement first. We would rather solve one thing well and let you decide whether there is a second conversation.
- Free
Production-readiness audit
Paste a URL, get the report in a minute. No account, no call.
Run the audit - One call
Fix one problem
You are here. Tell us the symptom, find out what it is, get an offer in writing.
You are here - From $500/mo
Fractional CTO
Unlimited written advice from an engineer who knows your system, or a weekly call on top.
See the tiers - Scoped
Sprint, migration or rebuild
Ten days to production, off Lovable to code you own, or an architecture review of an AI-written codebase.
See the options
How it works
- 01
Tell us the symptom
One paragraph is enough — the error, the screen, what you expected. Run the free audit first if you have not; it often names the problem for you.
- 02
A call, or a written reply
Thirty minutes to look at it together, or a written answer if you prefer. Either way you find out what it is before anything is agreed.
- 03
A written offer
After the call: the scope, the approach and what we need from you. Discussed on the call, confirmed in writing.
- 04
Fixed, explained, handed back
The fix in your project, a short note on what was wrong and why, and how to check it yourself — typically inside 48 hours of getting access.
What we promise before any money changes hands
We tell you what is actually wrong, whether it is one problem or a symptom of a bigger one, and what it would take — before you commit to anything. If the honest answer is that you can fix it yourself in an afternoon, that is the answer you get, and the instructions are usually on this page already.
Questions before you write
- Why is there no price on this page?
- Because the same symptom is twenty minutes in one app and two days in another, and a number invented before we have looked at yours would be wrong in one direction or the other. You get a call or a written answer first, then an offer with a real number in it. Nothing is agreed before you have seen both.
- Do I have to get on a call?
- No. Describe it in writing and you will get a written answer. The call is usually faster — most of these are diagnosed in fifteen minutes of looking together — but it is an offer, not a gate.
- What if my problem is not on the list?
- Describe it anyway. The eight here are what we see most, not what we can do. If it is one problem we can name, the process is the same; if it is bigger than one problem, you will hear that before anything is agreed.
- Which builders do you work with?
- Lovable, Bolt, v0, Cursor, Replit, Claude Code — and hand-written code, which is most of what we do the rest of the time. The stack underneath is usually React with Supabase, and that is the combination we know best.
- Do you need access to my code and database?
- To fix, yes — read access to the project, or a screen-share if you would rather not hand over keys. Both work. We tell you exactly what we need before you decide.
- How fast, really?
- 48 hours from the moment we have access, and often the same day. What takes time is usually waiting for access, so having it ready is the fastest thing you can do.
- What if the fix does not hold?
- We come back to it at no charge. If it turns out the problem was bigger than one thing, we stop and tell you what it actually is — the diagnosis is not something we bill for.
- No account to create
- An answer before an invoice
- We say when you can fix it yourself
Next step
Describe the problem in one paragraph.
We answer within a few hours with what it is, whether one fix covers it, and what we need from you.
