inparlor.
Development

Customer, Vendor & Dealer Portals.

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

By the numbers

  • 25+portals shipped
  • -40%support calls after launch
  • 6-12 wktypical build
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 catalogs
  • 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. 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. 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. 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. 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. 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.

Stack

Tools we run with, by default.

  • Next.js
  • TypeScript
  • Postgres
  • Auth.js
  • Clerk
  • S3-compatible storage
  • QuickBooks API
  • NetSuite API

We will work in your existing stack when it fits. We swap tools only when the cost of staying is higher than the cost of moving.

Pricing

Transparent, itemized, no day rates.

Custom quote

fixed price, scoped to you

Every engagement is scoped against your spec. Every proposal is itemized: design, build, content, and integrations — so you can sanity-check the math before signing.

Timeline

6 to 12 weeks

For mixed engagements (build + maintain), we bundle the proposal with a single price you can take to the board.

Featured work
Healthcare / Dental

2.3×

online bookings after rebuild

12-location dental group

12-location dental group with a fragmented web presence, a 4.1s LCP, and a booking flow that leaked 70% of visitors. We rebuilt the platform and booking experience; online bookings more than doubled, LCP dropped to 1.4s, and the group now runs on a 99.95%-uptime maintenance retainer.

Read the case study
Pair this with

Most clients run two or three of these together.

Stack thinking: paired engagements share one measurement layer, one accountability ledger, and one quarterly business review. That's where the compounding comes from.

FAQ

What buyers ask before signing.

Ready to start?

Ready to start with Customer, Vendor & Dealer Portals?

Get a proposal for Business Portals.

Name, email, and one line on what you need. Written scope, timeline, and price in 24–48 hours — no discovery call required to schedule a discovery call.

Response within 24 hours from a real strategist.