Services
Something's wrong? Tell mr-bill.
You don't need to know why something broke, only what you saw. Tell mr-bill in your own words. He finds the cause, fixes it, and checks the fix before it goes live.
- You sayWhat you saw, in your words
- He findsThe cause, not just the symptom
- The fixChecked before it goes live
Before and after
No developer on call, no agency waiting list, no code nobody understands.
When something in your software isn't working the way it should, you tell mr-bill what happened. He traces it to the real cause, makes a small, careful fix, and the fix gets the same review and try-out as everything else.
Here, a salon's booking form stopped sending: clients tapped Pay and it hung on Sending. He found the cause, fixed it, paid a test deposit on four phone sizes, and the fix went live the same morning.
How a fix happens
- 01
Tell him what you saw
Tell him what you did, what you expected, and what happened instead.
- 02
He finds the cause and fixes it
He finds the cause and fixes it. The fix is reviewed and tried out before it goes live.
- 03
Check it yourself
Check it yourself. If anything still looks off, say so in the same conversation.
What to tell him
Plain words are fine. The more of these you include, the faster he finds it.
Questions
Does mr-bill spot problems before I do?
Not today. When you notice something, tell him and he takes it from there. We'll say so here if that changes.
What should I include when I report a problem?
What you did, what you expected, what happened instead, and whether it happens every time. Plain words are fine.
Can a fix break something else?
Every fix is checked and tried out for real before it goes live, the same as a new feature.
What does it cost?
You add funds to your account and pay only for the work you ask for. You see the cost as it happens, and if your balance runs low the work pauses and asks before it continues.
