Menu
Speak to me directly+27 87 150 9305Tell me the problem

Home / Where should I start?

Not sure what kind of help you need?

Seven short questions about your business. You get a plain starting point, and nothing is sent unless you choose to.

Rather just talk? Call +27 87 150 9305.

The seven questions

  1. 01What’s missing
  2. 02Where it breaks down
  3. 03Where you’d see it first
  4. 04Which records are the real ones
  5. 05The first small result
  6. 06The riskiest part
  7. 07What you have ready

Already know the problem? Tell me the problem.

Answer all seven, then see your starting point.

Question 1 of 7: What’s missing right now?

Pick the one closest to your problem. You can change it later.

For your technical person

What is missing today? Choose the answer closest to the problem. You can change it later.

  • A new workflow or tool. The work is manual, scattered, or not supported by a suitable system.
  • A reliable system connection. Two or more systems need to exchange the right information.
  • A capability in an existing platform. WordPress, WooCommerce, or Shopify is missing a specific behaviour.
  • Confidence in software already started. The current code is inherited, stalled, fragile, or AI-built and needs an evidence-led decision.
Question 2 of 7: Where does the work actually break down?

Think about where things get delayed, done twice, or lost.

For your technical person

Where does the work break down? Think about the handoff that causes the most delay, rework, or uncertainty.

  • Inside a manual process. People repeat steps, chase updates, or maintain spreadsheet and email workarounds.
  • Between existing systems. Records disagree, exports are manual, or updates arrive late.
  • Inside a store or website flow. The platform works, but its customer, admin, or checkout journey does not fit.
  • Inside software nobody can safely continue. The demo works, but launch, changes, ownership, deployment, or support have become risky.
Question 3 of 7: Where do you want to see the first improvement?

Where would you notice it first?

For your technical person

Where should the first useful result live? Choose the place where the improvement needs to be visible first.

  • In a focused web application. A team needs one shared screen, dashboard, portal, or workflow.
  • Across two or more systems. The improvement is a business process that spans existing software.
  • Inside the existing platform. Customers or administrators should use it within the current site or store.
  • In the current codebase and deployment. The first result is control of what exists and a responsible path forward.
Question 4 of 7: Which system should stay in charge of the real records?

When two places disagree, which one do you believe?

For your technical person

What should remain the source of truth? This is the system that should own the important records and rules.

  • The new focused application. The tool needs its own records, rules, permissions, and shared state.
  • An existing business system. A CRM, ERP, payment service, or external API already owns the data.
  • WordPress, WooCommerce, or Shopify. The current platform should remain at the centre of the workflow.
  • That is not clear yet. Ownership, data boundaries and operational dependencies must be established before more work.
Question 5 of 7: What should the first small result prove?

Pick the smallest result that would already be useful.

For your technical person

What should the first working slice prove? Pick the smallest result that would make the project useful.

  • One complete user outcome. A person can finish one important workflow from start to finish.
  • One dependable data flow. One system pair exchanges validated data that can be reconciled.
  • One working platform behaviour. One missing screen, rule, plugin, or extension works in the real platform.
  • One written readiness decision. The evidence supports a continue, harden, selectively rebuild, replace, or stop decision.
Question 6 of 7: What’s the riskiest part to get right first?

The part that would hurt most if it went wrong.

For your technical person

What needs the most technical attention first? Choose the risk that should be resolved before the project expands.

  • Workflow and scope clarity. The users, decisions, and acceptance boundary need to be made explicit.
  • Data reliability and ownership. The flow needs validation, retries, failure handling, and reconciliation.
  • Platform constraints. Plans, APIs, hooks, permissions, or staging access may shape the solution.
  • Production risk and operational ownership. Access, security boundaries, deployment, rollback, maintainability and support need review.
Question 7 of 7: What do you already have ready to go?

You don’t need everything ready. Pick what’s closest.

For your technical person

Which starting point is closest to ready? You do not need everything prepared to send a project enquiry.

  • The workflow is understood. You can name the users, inputs, decisions, and useful output.
  • The systems are known. You know the systems, data objects, and access needed for the first flow.
  • The platform is known. You know the platform, plan, current setup, and missing behaviour.
  • The software and accounts can be accessed. The repository, deployment, data and third-party services can be inspected legally.
Start again

Your answers stay in this browser unless you choose to send them with a message.

Four common places to start.

Most problems cross more than one. The guide finds the most useful first piece, so the first conversation is about your business, not about technology.

  1. Build one simple tool for the job.

    The first piece: One screen for one job, such as a booking list, an order form or an approval, working from start to finish.

    How I build a simple business tool

  2. Connect the systems you already have.

    The first piece: One connection between two systems you already use, such as your store and your accounting, with a check that both sides agree.

    How I connect business systems

  3. Add the missing piece to the site you already have.

    The first piece: One missing feature, such as a checkout rule, a customer screen or an admin page, built and tried on a copy of your site first.

    How I add to an existing site or store

  4. Get an honest answer about the software you have.

    The first piece: A written review that says plainly: keep it, fix it, rebuild part of it, or stop spending. It lists what was checked and what wasn’t.

    How I rescue a software project
For your technical person

The guide is the Build, Connect, Extend or Rescue model. Each answer scores one path: question 1 is worth 3 points, question 2 is worth 2, and the other five are worth 1 each. The highest total wins; a tie goes to Build, then Connect, then Extend, then Rescue.

Build: a new application owns the workflow, records, rules and user experience. Focused business tools

Connect: existing systems stay in place while a dependable integration moves and validates data between them. API and integrations

Extend: WordPress, WooCommerce or Shopify stays central while a focused capability is added around it. Custom platform apps

Rescue and productionise: existing software is inspected before a launch, takeover or rebuild, producing a risk-ranked decision about what can responsibly continue. Rescue a failed project

Privacy: the answers live in the browser (React state) and this tab's session storage, and are sent only if the visitor submits the form at the end, through the same guarded lead pipeline as every other form, with the recommendation and the seven answers in the message.

Already know what’s wrong? Tell me in your own words.

+27 87 150 9305

Monday to Friday, 09:00 to 20:00 SAST. Or email info@antondevilliers.com.

Tell me the problem Call +27 87 150 9305
Tell me the problem

Step 1 of 3. Pick what’s closest. You can explain in your own words next.

I reply myself, usually the same working day. The first conversation is free, and you’ll know the price of every piece before it starts. How a project works · Privacy

WhatsApp