Skip to content
BOOK A 20-MINUTE CALL
hello@seamwire.com
SERVICE · WEBSITES · CUSTOMER PORTALS

Customer portal development that answers before they call.

Seamwire builds customer and client portals for B2B companies: one secure login where your customers see their orders, invoices, documents and delivery status, and reorder without emailing anyone. The portal reads straight from the systems you already run, such as your ERP, CRM and accounting, so it shows the same figures your team sees. We design it with the people who answer customer calls today, because the questions they hear most are the ones the portal should answer first.

Start with a 10-day first stepWebsite design & development
FIRST STEP
10 working daysOne process, mapped and shown working, with a business case and a dated plan.
TEAM
3–5 peopleA dedicated team from our 50+. The people who scope it build it.
OWNERSHIP
YoursCode, data and accounts are yours from the first commit. No lock-in.
01

SIGNS YOU NEED THIS

  1. 01Customers phone or email to ask where their order is.
  2. 02Account managers spend their day resending invoices, certificates and delivery notes.
  3. 03Reorders arrive as emails, PDFs or photos of an old order form.
  4. 04Each customer has its own prices, and your website cannot show them.
  5. 05Your customers' buyers want answers outside your office hours.
  6. 06Documents go out by email, so nobody knows which version the customer is using.
02

WHAT WE BUILD · CUSTOMER PORTAL DEVELOPMENT

03

SYSTEMS AND TOOLS WE COMMONLY WORK WITH

BUILD
  • Next.js
  • React
  • TypeScript
  • Node.js
  • PostgreSQL
READS FROM
  • SAP Business One
  • NetSuite
  • Microsoft Dynamics 365
  • Odoo
  • Salesforce
  • HubSpot
  • Xero
  • QuickBooks
  • carrier APIs
SIGN-IN AND SECURITY
  • Microsoft Entra ID
  • Google sign-in
  • single sign-on (SAML, OpenID Connect)
  • multi-factor authentication
PORTAL PLATFORMS, WHEN THEY FIT
  • HubSpot customer portal
  • Salesforce Experience Cloud
  • Shopify B2B
  • Odoo portal

We pick tools for your situation, not ours. If something you already run does the job, we keep it.

04

HOW IT WORKS

  1. 01

    A 10-day first step

    One process or page, mapped with the people who do the work and shown working. You leave with a business case and a dated plan, and keep everything it produced.

  2. 02

    Build in short, visible steps

    Working software every week or two on a staging site you can click, with weekly written notes on what moved and what we need from you.

  3. 03

    Launch and hand over

    Released carefully, with monitoring switched on, then a handover pack: code, docs, runbooks and a session with your team.

  4. 04

    Look after it

    Support, monitoring and improvements on terms agreed in writing before we start, with a named team who knows the work.

The full approach, phase by phase
05

WHERE WE DO THIS MOST

01ManufacturingTYPICAL FIRST STEPConnect one line's output to your stock figures, so what you promise matches what you can make.02Logistics & supply chainTYPICAL FIRST STEPWire your dock scans to customer tracking, so “where is it?” answers itself.03Retail & e-commerceTYPICAL FIRST STEPConnect the order desk to the warehouse so stock is never promised twice.06Professional & financial servicesTYPICAL FIRST STEPTake one intake process from inbox to filed and approved, with every step logged.07Ports: shipping & freight forwardingTYPICAL FIRST STEPPull your carriers' milestone updates into one timeline, so every ETA your customer sees is the latest one.
06

QUESTIONS BUYERS ASK

What does a B2B customer portal include?
Usually five things: order status and tracking, reorders at the customer's own prices, invoices and statements, a library of documents such as certificates and drawings, and a way to raise requests like returns or quotes. We start with the questions your team answers most often by phone and email, build those first, and add the rest once customers are using it.
Which systems does the portal read from?
Whichever already hold the answers: your ERP for orders, stock and prices, your CRM for accounts and contacts, accounting for invoices and balances, and carriers for tracking. The portal reads from them rather than keeping a separate copy, so a customer never sees a status your team cannot. Where a system has no API, we use exports or a small connector and tell you its limits.
How do logins, roles and security work?
Each customer company gets an account with its own users. Roles decide who sees prices, who can place orders and who can only download documents, and the customer's admin manages their own people. We support multi-factor sign-in and single sign-on, log every action, encrypt data in transit and at rest, and test that one customer can never see another's records.
Does the portal work on a phone?
Yes. We design it for a phone first, because a site manager checking a delivery or a buyer approving a reorder is rarely at a desk. Everything works in the phone's browser, with no app to install. If your customers need offline use or barcode scanning, we will talk through a native app, but most portals do not need one.
Should we use portal software or build a custom portal?
If your CRM or e-commerce platform already includes a portal and it shows what your customers ask about, use it, and we can set it up for you. Build custom when the answers live across several systems, when prices and permissions differ for each customer, or when the portal must follow your processes rather than the vendor's. We compare both routes in the first step.
Can the portal work with our CRM and website?
Yes. It can sit at your own address, such as portal.yourcompany.com, match your website's design, and share contacts with your CRM so someone added by sales can be invited straight in. What customers do in the portal, such as reorders and requests, flows back to the CRM, so account managers see each customer's activity without asking.
Who owns the portal and the data?
You do, from the first commit: the code in your repositories, the portal in your hosting account and the data in your own systems. There is no licence to us and no lock-in. We hand over documentation and runbooks written so your own team, or another supplier, could look after it.
07

GUIDES

01ERP integration for manufacturers: what it involves and where to startEXPLAINER · 7 MINA plain guide to ERP integration for 50–500-person manufacturers: which flows to connect first, how machine and shop-floor data reaches the ERP, common systems (SAP Business One, Dynamics, Odoo, Tally), and the pitfalls.02Build or buy: when a custom internal tool beats off-the-shelf softwareDECISION · 5 MINA practical way to decide between buying software and building a custom internal tool: the questions to ask, the hidden costs on both sides, and when a hybrid (buy, then connect) is the best answer.03How to choose a custom software development company: 12 questions to askCHECKLIST · 6 MINTwelve questions to ask before hiring a custom software development company or agency, from who owns the code to how they handle security, handover and what happens after launch.

YOUR FIRST STEP

Start with one process, working in ten days.

Tell us where it slows down. We map it with your team, show it working, and hand you a business case. If the numbers do not work, you keep everything it produced.

Tell us where it slows down