Professional services: the workflows behind the billable hour

What this sector runs on

Professional and business services here means management consultancies, accounting and advisory practices, marketing and creative agencies, architecture and engineering practices, and specialist B2B advisers. Legal practices and recruitment firms are classified separately in the OutsourcingVN taxonomy and are not covered here.

These firms sell time and judgement. Three things carry the business: the client relationship, the document produced for it, and the record of hours behind both. The operating constraint is attention — whose attention was spent, on what, and whether the client agreed to it first.

Current pressures

What a managing partner or operations director describes as pressure in 2026:

The workflows a project touches

Five workflows carry almost every project in this sector:

1. Pursuit to engagement. Opportunity, conflict check, proposal, scope, engagement letter. The scope written here is what every later dispute is measured against.
2. Engagement delivery. The client file: working papers, versions, internal review, approval, the deliverable that leaves the building.
3. Time to invoice. Capture, work in progress, billing and recovery. Mechanically this is the back-office matching problem described in ERP and back-office operations, with time in the place of stock.
4. Client communication and status. Intake, questions, chasing missing information, status. The queue mechanics are on customer support automation.
5. Knowledge reuse. Methods, precedents and past deliverables, findable and safe to reuse.

Data and confidentiality constraints

• Confidentiality is the product, not a policy. Client segregation, conflict walls and per-engagement access are design inputs on day one, not hardening at the end.
• Retention is set by your client contracts. Different clients impose different retention and deletion terms, and the strictest term that applies drives the data model.
• Client files contain personal data. Names, financial detail and sometimes health or employment data sit inside working papers, which makes deletion and export a specified feature rather than an afterthought.
• Model vendor terms are a contract question first. Whether a provider may retain or train on client content is answered in writing before a design exists.
• Access follows the engagement, not the employment. Rights end when the engagement ends. One directory, reviewed per engagement.

Published security practice is specific and limited: secure code review and version control, role-based access control, multi-factor authentication on admin dashboards, contributors under non-disclosure agreement, and data-processing agreements on request. Netbase JSC holds ISO 27001 certification for information security management and a SOC 2 Type II attestation; no certificate number, date, auditor or audit scope is published, neither extends to your systems, and neither is a professional or industry accreditation for the regulated work you do.

Where AI changes this work, and where it does not

This is where the published record transfers most directly. For a client that is not named, Netbase built a WhatsApp Business AI chatbot with intent and conversation-flow handling, an LLM API and CRM synchronisation for lead capture, customer data and workflow automation. It was delivered in milestones from design and prototype to documentation, knowledge transfer and 30 days of support, over four to eight weeks. Netbase has also delivered anonymised client AI projects including retrieval-based knowledge assistants, document AI and MLOps pipelines.

The help desk and CRM Netbase deploys for business partners, described below, is close to what a firm buys: intake and status conversations that update the client record, retrieval over methods and past deliverables, and extraction from documents the client sends in. What the chatbot record does not contain is a measured business result, a named client or a sector, and no human hand-over behaviour is claimed for it. Judgement, review and sign-off stay with named people; delivery is remote-first from Hanoi in Agile increments with weekly reviews, using AI-assisted engineering under human review.

Which route applies to your problem

Netbase's delivery lifecycle: discovery and strategic alignment; team assembly and architecture planning; agile execution with outcome-based milestones; modular components; training and rollout; ongoing support. In a firm, discovery observes a busy week instead of running workshops, and rollout starts in one practice once a billing cycle closes. Most engagements are agreed as fixed-scope contracts after discovery.

• If you cannot yet say which task to automate, start with the AI workflow blueprint, a bounded assessment whose output you can take anywhere.
• If the task is already clear — intake, status, document extraction, drafting support under review — the build route is AI workflow automation. The full offer list, and where a quotation starts, is the services page.
• If the constraint is the client queue or the time-to-invoice chain, read customer support automation and ERP and back-office operations first; the workflow page is usually the more useful read.
• If the sales and client-request queue itself needs a system, Cloodo, a Netbase Business Division, runs this help desk and CRM for business partners — ticketing, a knowledge base, lead capture and quotes in one dashboard — scoped through AI workflow automation.
• If the constraint is technology leadership, not a build, fractional CTO and AI transformation advisory is a monthly retainer of agreed days over a 3 to 12 month term, with a handover to a permanent hire.

Where OutsourcingVN fits, and where it does not

It fits software and automation around your own operations: intake, client communication, document handling, knowledge retrieval, time capture and the reporting on top. It fits integration between the tools a firm already runs.

It does not fit your professional work. Netbase does not give regulated advice, does not sign or review a client deliverable, and is not a licensed adviser of any kind. Delivery is remote-first, with Netbase accountable while a team may combine Netbase staff, approved specialists or disclosed partners, and no office or standing capacity outside Hanoi is published. That accountability is set out on the project delivery page. Training providers, whose record is a credential rather than a billable hour, are covered under education and training.

Which published records apply to a firm

The published records closest to a firm's work are close in mechanics: the chatbot record above, which is client communication with a CRM behind it, and the anonymised AI project types, which are retrieval, document handling and the pipeline that keeps them running. The chatbot record is written up in full as a WhatsApp AI chatbot with CRM integration. Practice management, engagement management and time and billing systems are scoped in discovery from those mechanics and the workflows above. Other records are on the work page.

Client count describes company scale. Netbase has served more than 500 clients in the United States, Europe and Asia-Pacific, most from outside Vietnam, as service markets rather than offices, and publishes no project or country counter; consulting and outsourcing joined its e-commerce origins in 2016.

So ask for four things instead of a client list from your own sector: a named delivery lead and a named engineer accountable for every change; a discovery output another supplier could use without rework; a pilot on one practice through one full billing cycle, with a rollback; and written answers on data retention, model vendor terms and deletion before any design is approved. How evidence is labelled here is on the methodology page.