What is going wrong? Start here

How to use these pages

Pick the page whose title sounds most like what you would say on the phone: "the developer has stopped replying", "orders are missing from Tally", "Google has stopped sending visitors". You do not need to know what the fix is called. The pages are grouped by where the trouble shows up:

• Software and apps. Something you had built, or a tool the team relies on, has stopped coping: a spreadsheet, a no-code product, an app waiting for store approval, a project whose developer has gone.
• Online stores. The shop takes orders, but something around it fails: speed, or the link to accounts and stock.
• Search and visibility. People cannot find you, on Google or in AI answers, or far fewer of them do than before.

What each page gives you

Every page follows the same pattern, so you can scan it quickly:

1. The symptoms, so you can confirm you are on the right page.
2. The usual causes, in the order to check them. The checks that cost nothing come first.
3. A check you can run yourself for each cause, using tools you already have: your own admin screens, Google Search Console, the rejection email, one failed order.
4. What fixes it, including the cases where the fix is a setting and not a project.
5. When to get help, and what to have ready so the first conversation is useful.

You may not need a developer

Several of these problems are solved by a setting, a form in a console, or a cheaper ready-made product, and the pages say so where that is the case. Work through the checks first. If you reach the end with the cause identified, you will get a faster and smaller quote from anyone you ask. If the checks do not explain it, that is the point at which a technical assessment earns its cost.

If your problem is not listed

Use the custom requirements page to describe it in your own words. If the trouble is with software someone else built and no longer supports, start with software rescue. If a term on any page is unfamiliar, the glossary has short definitions.