Sound
familiar?

We get access, review the code and hosting, and write down what is actually there. Then you get a plan: finish it, fix it or rebuild it, with a price for each.

1. Recover access to code, hosting and domains
2. Review what exists and what works
3. One-page plan with three options
4. Finish the work with weekly updates

We read the code, draw the map and write the manual it never had. After that it can be maintained by us or by anyone else you choose.

1. Read and document the system
2. List the risks, most urgent first
3. Fix the dangerous ones
4. Move to a care plan or hand over the documentation

We move it somewhere safe before that computer fails: a proper installer, a server or the cloud, with a backup. If it cannot be moved, we rebuild the part that matters.

1. Take a full backup first
2. Work out what it depends on
3. Move or rebuild
4. Install for everyone who needs it

We turn it into a small web app with the same columns you already know, plus user permissions, history and backups. The spreadsheet keeps working until the day you switch.

1. Map what the spreadsheet really does
2. Build the app around the same columns
3. Import the existing data
4. Switch over on a quiet day

If a person is copying data between two screens, software can do it. We connect the systems so information is entered once and appears everywhere it is needed.

1. Watch the job being done by hand
2. Connect the systems directly
3. Run old and new side by side
4. Switch off the manual step

We connect each marketplace, match every payout to its orders, fees and refunds, and push clean entries into your accounting. You see one dashboard instead of five exports.

1. Connect each sales channel
2. Match payouts to orders, fees and refunds
3. Post clean entries to accounting
4. One dashboard for what is still unmatched

We build one place where sales, fees, refunds and payouts arrive on their own and are already matched. Month end becomes checking the exceptions, not building the report.

1. List every source of numbers
2. Automate the imports
3. Match and flag the exceptions
4. Reports ready on day one

We pick the right payment provider for your country and customers, set it up, connect it to your invoices and accounts, and test it with real transactions before you announce it.

1. Choose the provider
2. Set up checkout or payment links
3. Connect to invoices and accounting
4. Test with real payments

We add monitoring that checks the site every minute and alerts a person, set up tested backups, and take responsibility for getting it back up. You hear about problems from us, with the fix already under way.

1. Monitoring on every important page
2. Backups, restored once to prove they work
3. A named person on call
4. A monthly report

We audit the account, explain every line in plain English, remove what is not used and move what is overpriced. You get a one-page map of what runs where.

1. Audit every server and service
2. Explain each cost
3. Remove or resize
4. Document what is left

Small tools should take weeks. We agree the three things it must do, build those well, and leave the rest for later. You use it while it is still useful to learn from.

1. Agree the smallest useful version
2. Fixed price and date
3. Build and show progress weekly
4. Hand over with a walkthrough

We build the smallest version that real customers can use and pay for. If it works, we grow it. If it does not, you found out cheaply.

1. Cut the idea to its core
2. Build a first usable version
3. Put it in front of real users
4. Decide the next step from what happens

That is the Dedicated plan: the same person, a fixed number of hours each week, working inside your tools. You keep a running list and it gets done in order.

1. Agree the weekly hours
2. Shared task list
3. Weekly summary of what was done
4. Change the hours month to month

A daily job like that is the easiest thing to automate. We build it to run on its own each morning and send a message only when something looks wrong.

1. Record the daily routine
2. Automate each step
3. Alert only on problems
4. Hand back the hours