inparlor.
Australia

Customer, Vendor & Dealer Portals.

Self-serve portals that take the phone calls out of doing business with you.

Pricing

Custom quote — proposal within 48 hours

fixed project

Indicative AUD conversion; final quotes are issued in AUD against itemised scope.

Why AU buyers choose us

A US-headquartered senior team building software for Australian businesses, with working hours that overlap AEST, quotes in AUD, and the Privacy Act 1988 built into how we handle data.

  • AEST overlap windows for live calls, demos, and sprint reviews — not just async email
  • Quotes and invoices in AUD, GST shown clearly as a separate line, never buried
  • Privacy Act 1988 and Australian Privacy Principles considered in every data model we ship
  • You own the GitHub repo and deployment from day one — no offshore black box, no licence trap
  • Senior engineers only on the build, the same people who scope the work do the work

We design to the Privacy Act 1988 and the 13 Australian Privacy Principles, keeping personal data handling, consent, and breach-notification posture in scope from the data model up. Every quote separates GST as its own line so the price you approve is the price you pay.

What this includes

Deliverables, line by line.

  • Two-week paid discovery with a fixed-bid proposal at the end
  • Role and permission model mapped to your account types
  • Authentication and account provisioning via Auth.js or Clerk
  • Customer portal: orders, invoices, documents, and support tickets
  • Vendor or supplier portal scoped to your procurement flow
  • Dealer or partner portal with tier-based pricing and protected catalogues
  • Document storage on S3-compatible object storage with access controls
  • Live integration to QuickBooks or NetSuite for invoice and order data
  • Admin console for your team to manage accounts, tiers, and content
  • Production deployment with staging, plus source in your GitHub org
Process

How an engagement runs.

  1. 01

    Discovery

    Two weeks, paid. We map every account type that touches the portal, the actions each one needs, and where the data lives today. You leave with wireframes, a permission matrix, and a fixed-bid proposal.

  2. 02

    Auth and data foundation

    Sprint one stands up authentication, the role model, and the connection to your ERP or accounting system. Reading real invoices and orders into a staging portal is the milestone, not a mockup.

  3. 03

    Portal build

    Two-week sprints build out the screens each account type uses, with a Loom demo every Friday and a staging deploy you can hand to a friendly customer to pressure-test.

  4. 04

    Integration hardening

    We make the sync two-way where it needs to be, handle the failure cases when your ERP is down or returns garbage, and add audit logging so you can answer who saw and did what.

  5. 05

    Rollout

    We launch to a pilot group of accounts, watch the support load, and fix the rough edges before opening it to everyone. A 60-day stability window follows where we sit on call for issues.

FAQ

What buyers ask before signing.

Ready to start?

Ready to start with Customer, Vendor & Dealer Portals?

Tell us about your business and current numbers. We respond within 48 hours with scope, pricing in AUD, and timeline.

Get a proposal