Custom web application architecture advisory

A structured consulting engagement that defines module boundaries, data ownership, integrations, and a delivery sequence for your custom web application.

Who this is for

Owners, operations managers, and technical leads at Australian small businesses who are commissioning or rebuilding a custom web application and need an independent architecture view before coding velocity takes over.

You might be choosing between an agency and an in-house hire, arguing about whether to split a monolithic admin tool, or inheriting a half-finished portal with no clear seams. This advisory is designed for those moments.

Result you leave with

A written architecture note that covers:

  • Who the application serves and which jobs it must protect first
  • Proposed module boundaries and ownership of core data
  • Integration points with accounting, identity, payments, or industry systems you already use
  • A staged delivery sequence suited to a small team
  • Open risks, assumptions, and decisions that still need your sign-off

We do not write production code in this engagement. We prepare the decisions that make later code cheaper and clearer.

What is included

  • Kick-off briefing (video or Sydney office)
  • Document and codebase skim where access is granted
  • Two working sessions for diagramming and trade-offs
  • Draft architecture note for your comments
  • Final note plus a short decision log
  • One follow-up clarification call within 14 days of delivery

What is excluded

  • Hands-on implementation or pair programming
  • Vendor selection bake-offs billed as separate procurement work
  • Ongoing retainer support (available after the advisory if useful)
  • Legal or security certification audits

Provider and approach

Sessions are led by LeafHub’s principal advisor. We work in plain language with your operators in the room — diagrams stay readable by non-engineers when decisions affect them.

Process and timeline

  1. Intake — you send goals, constraints, and any existing diagrams or tickets.
  2. Discovery — we interview stakeholders and inspect what already exists.
  3. Structure — we propose boundaries and sequence; you challenge them.
  4. Handoff — final note delivered; clarification call scheduled.

Most engagements finish in two to four weeks depending on stakeholder availability.

Preparation

Please gather: a one-page description of users, a list of systems the application must talk to, rough budget and timeline, and access to any staging environments you are willing to share under NDA.

Constraints

We advise on architecture and delivery shape. We will not rubber-stamp a predetermined vendor stack if the evidence points elsewhere. If the right answer is “buy more, build less,” we will say so.

Pricing basis

Engagements start from AUD 4,800. Larger multi-product estates or heavy integration inventories are quoted after the briefing call. See Rates for related formats.

Next step

Request a briefing call and mention “architecture advisory.” We will confirm fit and propose dates.