KJ King Consulting

Custom Business Operating Systems

Build a complete operations portal around the way your company works.

Operations team reviewing a workflow in a warehouse

Build the customer and operations experience your business actually needs.

For teams whose client updates, documents, approvals, schedules, and billing live in disconnected systems.

What we can scope

  • Delivery workflow map
  • Customer and staff experience
  • Integration and launch plan

From workflow discovery to the first portal release

Choose a representative workflow from the first customer request through the final status, approval, or invoice. Bring the existing tools and name the source of truth for each record. Identify what customers should see, what staff need to change, and how exceptions are assigned.

Choose a complete customer journey

Find one workflow that staff and customers repeat. Walk through its first request, assignment, status changes, approval, and final record. Identify the decision the customer expects to make at each stage. Use that map to decide what belongs in the staff workspace and what the customer should see.

Design the record and permission model

Give each important record a source of truth. Decide which fields can be synchronized and where updates are approved. Inventory each role and test permissions against its actual jobs. Account for external collaborators, clients with multiple locations, departing staff, and audit history.

Accept the release using real situations

Test on desktop and mobile using representative examples. Walk through a reassigned request, an expired invitation, a rejected approval, and an unavailable integration. Export a completed record and ask the team to explain how they would resolve a mismatch. Approve rollout when the normal and exception paths are usable.

Hojas public concept homepage and pickup entry points

Related project

Hojas Tea House

Hojas public concept homepage and pickup entry points.

Explore the case study

Try the sample workspace

Interactive workspace demo

Sample data · Changes stay in this preview

Operations workspace

Sales & CRM

The sample CRM shows qualified lead intake by week. Quotes and approvals are separate totals for the same six-week period.

Harbor SupplyNew lead

A sample buyer requested a quote for a multi-site installation.

Qualified leads
128
Quotes issued
34
Quotes accepted
12
New qualified leads · six sample weeks
01530Week 1: 16 leadsW1Week 2: 19 leadsW2Week 3: 18 leadsW3Week 4: 23 leadsW4Week 5: 25 leadsW5Week 6: 27 leadsW6
View chart data
PeriodNew qualified leads
Week 116
Week 219
Week 318
Week 423
Week 525
Week 627

What a good handoff looks like

Discovery produces a phased roadmap, role and permission model, integration boundaries, and acceptance criteria. The first release should let a customer and staff member each finish a meaningful task and see the correct status without relying on separate manual updates.

Try this before a consultation

Sketch a record for one customer request, including the staff owner, customer-visible status, approval history, and next action. Trace what happens when ownership changes or an attachment must be restricted. Use the sketch to define your first acceptance test.

Questions to ask before committing

How do I decide which existing systems to keep?

Identify the systems with reliable records, active integrations, or critical workflows. Keep the system of record where it already works and integrate selectively. Move a workflow only when the benefits justify migration, user training, and maintenance.

What belongs in a portal development quote?

Look for the included workflows, user roles, integrations, migration boundaries, acceptance criteria, and responsibilities for ongoing operations. Request a realistic demo of one end-to-end scenario before assigning value to a long feature list.

Related expert answers

Browse state and city service pages