Traffic arrives and leaves
Visitors reach the store. Most never reach checkout. The cause sits in mobile layout, unclear navigation, thin product pages or missing trust signals. Rarely in ad spend.
Shopify development, custom websites, internal software and AI automation. I start with the problem, not the technology. Eight years building e-commerce, and I run my own store.
Reply inside one business day. No retainer required to start.
None of them look urgent on a dashboard. All of them compound. The audit exists to find which one costs you most.
Visitors reach the store. Most never reach checkout. The cause sits in mobile layout, unclear navigation, thin product pages or missing trust signals. Rarely in ad spend.
Support answers the same six questions. Order data gets re-typed into a spreadsheet. Reports get rebuilt by hand. Repetitive work grows with the business, and it eats the owner first.
A lead fills in the form. Nobody follows up on day three. The work goes to whoever replied first. Most businesses lose more revenue to silence than to price.
Three leaks, priced per year. Pick a business shape if you do not know your figures, or open the sliders and use your own. Nothing gets sent anywhere, and nothing here is a promise.
Loading assumptions.
These are typical starting assumptions, not measurements of your business. Switch to Use my numbers to replace every one of them.
Relative, not absolute. A 20% uplift moves a 1.4% rate to 1.68%.
Use your own opportunity cost if the work lands on you.
Count enquiries only. Completed orders sit in leak 01.
Pricing below is a starting range in Australian dollars. Scope, integrations and third-party costs move the number, and I confirm those before quoting.
Find the blockers before spending on a build.
Fix one contained problem, fast.
Rebuild one expensive process.
Run the business on one system.
The audit fee comes off the build. If the audit finds nothing worth fixing, you keep the report and owe nothing further.
A call, then a review of the store, the workflow and the numbers. You get a ranked list of problems. No build proposed yet.
Pick one problem. Define what changes, what stays, who supplies content and credentials, how many revisions, and where the project ends.
Production-ready output, modular, delivered in phases. You see working progress, not a black box and a launch date.
Documentation, a recorded walkthrough and a warranty window. You own the code, the repository and every account.
Optional retainer for fixes, improvements and continued optimisation. Month to month, cancel any time.
Four ventures run under my own name. Every one ships real product to real customers, which is where the operational lessons come from.
Shopify store shipping live aquatic plants and livestock Australia-wide. Eight years of Dawn theme, Liquid, Admin API and Storefront API work sits behind it.
Compatibility and recommendation engine for planted tanks. Scores every pairing against water parameters and returns a verdict, a score and the reasoning behind it.
React PWA coding agent for Shopify work. Dual system prompts, voice input and a job queue. Built to speed up client delivery, then kept.
Aquatic fertiliser line. Formulated, branded, packaged and sold through the store. Product work, not a landing page.
I run a store where the product dies if a parcel sits in a depot over a long weekend. Stock, fulfilment, refunds, seasonality and support load stopped being abstractions years ago.
That constraint shapes how I build. Systems get boundaries. Automated decisions get confidence thresholds and a human escalation path. Nothing ships on a promise it holds under load.
A$299, delivered inside a week, credited against whatever gets built next. You get a ranked list of what costs you money and what it takes to fix each item.
The goal is not more software. The goal is less friction, recovered revenue, and your time back.