Customer portals & accounts
Sign-in, account-specific content, user roles and customer workflows. Access rules and the sensitivity of the data shape the implementation and quote.
WEBSITES / 03 — CUSTOMBACK TO THE STUDIO ↗
When a website
becomes a system.
Accounts, data and workflows that need to work together. A considered plan for the way your business actually operates.
01defined scope
02clear proposal
03agreed milestones
The connections
change the project.
The important question is how the features depend on one another. A button can be an add-on. A flow that needs accounts, permissions, data and recovery deserves its own plan.
- Customers log in and see information specific to them
- Orders, stock, payments or bookings need to stay in sync
- Your team needs a dashboard, permissions or a bespoke workflow
A scope shaped around you.
We choose the features your project needs and quote them together. The starting price does not include every system listed below.
- Full e-commerce systems
- Customer accounts & portals
- Custom databases
- Custom dashboards & permissions
- Advanced booking systems
- Complex payment workflows
- Bespoke integrations & automation
- Other custom web applications
01
Built around the job to be done.
Examples of work we scope individually. These are project types, not a list of everything included for A$999.
E-commerce & payment workflows
Catalogues, stock, orders, payment events, refunds and customer accounts. A hosted payment link alone remains an add-on.
Advanced bookings
Multiple staff or resources, service durations, availability, cancellations, deposits and reminders working as a connected process.
Databases, dashboards & integrations
Custom records, internal tools, third-party APIs and automated workflows. Data volume, access permissions and failure handling are considered together.
02
From A$999. Defined before development.
A starting point for a tightly scoped custom project. Larger systems are quoted individually.
What shapes the quote
User roles, screens, data models, external services, migration, payment logic, security requirements and the level of testing and support needed.
What the proposal covers
Deliverables, what is excluded, dependencies, milestones, revision allowances, handover and the support period. We agree these before development.
Running costs stay visible
Hosting, databases, storage, paid APIs, messaging, booking tools and payment fees may create ongoing costs. They are separate from the build and identified during scoping.
03
A module or a system?
A useful distinction when you are deciding where to start.
Booking page → booking system
Embedding an existing scheduling page is an add-on. Custom availability, staff allocation, deposits, cancellations and reminder rules form a Custom project.
Payment link → order system
A hosted checkout or deposit button is an add-on. Stock updates, fulfilment, refunds and customer accounts connected through payment events form a Custom project.
FAQ assistant → business automation
An assistant answering from your business information is an add-on. An agent accessing private records or taking actions across business systems needs individual scoping.
Good to know.
01Does A$999 cover a complete e-commerce platform?
No. Custom starts at A$999 for a tightly scoped project. The features, integrations, data and support requirements determine the final quote.
02Can we build it in stages?
Where the dependencies allow it, yes. We can agree a useful first release and scope later stages separately, with the important architectural decisions considered upfront.
03What should I send with an enquiry?
Describe who will use it, what they need to do, the systems you use today, any timing or budget constraints, and what a successful first release looks like. Please do not send passwords or sensitive customer records in an initial enquiry.
Tell us what
you have in mind.
A little about your business, a few things you need. We’ll help turn that into a clear scope.
hello@midnightdesk.com