Bizcom Portal Roadmap

Updated: 2026-07-07

Purpose

This page records the current product direction for improving the Bizcom Portal after the July 2026 production feedback and usage audit.

The roadmap has two connected goals:

1. Make the portal more useful for Bizcom staff every day, so work moves through the system instead of being tracked in memory, chat, and spreadsheets.
2. Turn the client portal into a monitoring dashboard that clearly answers what Bizcom did, what the client's compliance status is, and why Bizcom is billing for the work.

Current Evidence

The July 7 production audit found:

• Production was healthy and docs were live.
• Five production feedback items still needed classification or follow-up.
• Only 9 staff/admin accounts showed active portal use in the previous 14 days.
• Daily active staff ranged from 0 to 5.
• Time tracking is being used, but several entries are implausibly long because timers appear to be left running overnight or for days.
• Feedback-to-Paperclip is deployed but not fully live until the Railway Paperclip environment variables are configured and verified.

Source report:

• /home/alex/.openclaw/workspace/reports/bizcom-production-feedback-usage-client-portal-audit-2026-07-07.md

Paperclip roadmap parent:

• RATA-759 - Bizcom roadmap: staff adoption, client portal monitoring, and Xero integration.

Roadmap Order

Gate 0 - Finish Feedback-to-Paperclip Verification

Paperclip: RATA-753

The integration code and database migration are deployed, but production and staging still need the Paperclip environment variables configured before end-to-end verification can pass.

Done means:

• A new portal feedback item creates a Paperclip issue.
• The feedback row stores paperclip_issue_id.
• Failure mode remains graceful if Paperclip is unavailable.

1. Clean Up Resolved Feedback

Paperclip: RATA-760

Update production feedback status only after explicit approval because this mutates live operational data.

Known classification:

• 6da7e503 project rename/description editing is resolved by the July 7 release.
• 9ebc5ce3 project creation invalid-data portion is likely resolved, while screenshot/paste support remains a separate new feature.
• 001fa961 Inara/My Day/Tasks access remains in progress until the affected staff session confirms the path.

2. Operations Adoption Dashboard MVP

Paperclip: RATA-761

This is the highest-leverage internal feature.

MVP should show:

• Daily active staff by day and person.
• Task completion and status-change count by person.
• Open and overdue workload by person and category.
• Bottlenecks: stuck tasks by assignee, client, category, and compliance step.
• Burndown: tasks created vs completed by week.
• Time-entry hygiene: missing time, active timers over threshold, and entries over 8/12/24 hours.

The dashboard should use audit, activity, task, and time-entry data. Login events alone are not enough because persistent sessions mean users can be active without a fresh login event.

3. Align My Day and Tasks Visibility

Paperclip: RATA-762

The current Dashboard/My Day and Tasks page do not describe the same work universe:

• My Day shows directly assigned tasks.
• Tasks can also show work for clients assigned to the staff member.

This can look like missing work or an access problem even when permissions are correct.

MVP should:

• Label My Day as direct assignments.
• Add or link a "Clients I support" section.
• Use the same monthly workload visibility model as Tasks.
• Add an admin diagnostic for why a user can or cannot see a task.

4. Time-Tracking Guardrails

Paperclip: RATA-763

Time data must be cleaned before it can support billing explanations or performance reporting.

MVP should:

• Warn after a configurable threshold, initially 4 hours.
• Require confirmation after 8 hours.
• Auto-stop, pause, or mark entries as needing review after 12/16 hours.
• Add an admin review workflow for long entries.
• Exclude unreviewed suspicious entries from client-facing summaries.

5. Client Portal 2.0 Monthly Monitoring Dashboard

Paperclip: RATA-764

Clients should not need to perform many actions. The client portal should primarily answer:

• What did Bizcom do this month?
• What is my compliance status?
• What documents did Bizcom complete or file?
• What am I paying for?
• What services am I not using yet but could benefit from?

MVP should use existing portal data first:

• This Month at a Glance: completed tasks, in-progress tasks, upcoming deadlines, and waiting-on-client items.
• Compliance status by service/category/month.
• Work completed with completion date, linked visible documents, and staff/time summary where reliable.
• Billing explanation using invoices plus supporting tasks, documents, and reviewed time.
• Documents delivered: filings, reports, receipts, forms, payroll outputs, contracts.
• Upsell preview cards for HR, Payroll, Finance/Xero bookkeeping, and compliance packages.

6. Xero Read-Only Integration Design

Paperclip: RATA-765

Xero should become the financial data backbone for client reporting, but the first phase should be read-only and auditable.

Design should cover:

• OAuth and tenant connection model per client.
• Read-only import of chart of accounts, contacts, invoices, bills, transactions, and relevant metadata.
• Mapping into a monthly client financial summary.
• Revenue, expenses, BIR-relevant summaries, and anomaly/missing-document indicators.
• Rate limits, token rotation, disconnect behavior, and audit trail.
• Staging proof using synthetic or explicitly approved test tenant data.

Do not start with two-way sync.

7. Feedback Screenshot Paste/Upload

Paperclip: RATA-766

Staff feedback says text-only issue reports are too weak for UI problems.

MVP should:

• Allow paste or drag/drop screenshot upload in the feedback modal.
• Store attachments using the existing safe upload/object-storage pattern.
• Keep privacy warnings visible.
• Show attachment links in admin feedback.
• Include attachment references in Paperclip issues only when the Paperclip integration is configured.

8. BIZCOME AI Intake Bot Discovery

Paperclip: RATA-767

The AI intake bot is a valid product idea, but it should follow the adoption dashboard and client portal work.

Discovery should decide:

• Whether the bot is for staff, clients, or admin triage.
• Which knowledge sources are allowed.
• Whether answers are draft-only.
• How permissions, audit trail, privacy, and hallucination controls work.
• Whether a prototype can use only sanitized docs and FAQ content.

Client Portal Product Direction

The client portal should become a monitoring and trust-building product, not just a request/action surface.

The ideal client experience:

• A client opens the dashboard and sees what Bizcom did this month.
• They see compliance status without needing to ask in chat.
• They see filings, reports, receipts, payroll outputs, contracts, and other completed documents.
• They can understand why an invoice exists because the portal shows work, docs, and reviewed hours behind it.
• They see upgrade paths for HR, payroll, finance, bookkeeping, and compliance services.

This also supports client acquisition. A prospect or current client should be able to understand that higher-tier Bizcom services create better visibility, fewer surprises, and cleaner operational records.

Implementation Rules

• Use staging-first PRs.
• Keep production/main/DB/env/Xero/credential changes approval-gated.
• Do not expose current time totals to clients until long timer entries are handled.
• Do not use real Xero tenant data without explicit approval.
• Keep Paperclip and docs linked whenever a roadmap item moves.