ExploreWhat I doWebsitesAppsAutomations and AIReady-made business toolsAccessibility checkLooking after it afterwardsProblems I fixMy workHow it worksFree website checkAboutAbout meCommon questionsGet startedRequest a free chatClient login
Light or dark

How I look after your project

Two things most small builders do not do: a full check of everything I build before your customers see it, and a private project page so you always know where it is up to.

Based in Adelaide, South Australia. I work remotely with businesses of any size across Australia.

Request a free chat

A full check before anything goes live

Before go-live, every website, app and automation I build is reviewed in five areas at the same time. Every finding is then challenged by a second set of reviewers who try to prove it wrong. Only what survives makes the report.

  1. Does it work correctly?

    Real bugs, anything that could lose your data, and the awkward cases: a wrong entry, a step that fails, the same record twice.

  2. Is it secure?

    The common ways sites get broken into, passwords or keys left in the code, private data showing where it should not, and add-ons with known safety problems. Anything that touches your customers, money or records must have a person's approval step and a record of what happened.

  3. Can it be changed safely later?

    How easy it is for me, or anyone after me, to change it without breaking something, and whether the checks that catch mistakes are in place.

  4. Is it built the same way throughout?

    Consistent code and styling, so it stays easy to look after.

  5. Does it work on every screen?

    I open the key pages in a real browser on a phone, a tablet and a computer. I look for errors, broken layouts and text that is hard to read. I also check that people using a screen reader can get around.

What you get: a plain-English report of what was wrong, what it could mean for your business, and what was done about it. Passwords and keys are never written into the report.

Plain limits: this is an AI-led review of the code and the live pages, not a certified penetration test (a paid attempt by a security specialist to break in). The add-on check is a best effort, not an exhaustive scan. No check can promise a site cannot be hacked.

Your private project page

Each client gets a private page at portal.botsandpieces.com.au. Type your email there and a private link arrives in your inbox.

  1. See progress

    Each stage of the build, what is done and what is next.

  2. Ask and comment

    Reply on the parts of the work I share with you, all in one thread.

  3. Your documents

    Quote, scope, agreement and handover notes, plus the files I share from your project folder.

  4. Send me files

    Upload photos, logos and documents straight into your project folder.

  5. Invoices

    See what has been invoiced, what is paid and what is left, with bank transfer details. Card payment is added once it is switched on.

  6. After it is live

    If you take a support plan, see your plan and what has been done each month.

No password to remember: you get a private link by email, and the page remembers your device until the link runs out. You can try a sample with made-up data now.

See an example project page

Common questions

Is the check a security guarantee?

No. It is a thorough AI-led review of the code and the live site, with every finding double-checked. It is not a certified penetration test, and no check can promise a site cannot be hacked. It does catch the common mistakes that get small business sites into trouble.

Do I pay extra for the check?

No. It is part of every build I do.

Will I see the report?

Yes. You get a plain-English summary of what was found and what was fixed before go-live.

When will the project page be ready?

It is being built now. Clients who start before it is ready move onto it when it launches, at no cost.

Can I still just use email?

Yes. The project page makes things easier; it does not replace a phone call or an email.