5 Questions Every CEO Should Ask About Their Operating Architecture Before 2027 Planning

October is planning season. Finance circulates the budget template, business units submit revenue targets, and IT sends over its list of "must do next year" projects. Every year, most of the meeting time goes to the question of what to do. Whether the current machine can actually run that plan usually gets one slide at the end.

Your operating architecture is how work really moves through the company: who initiates, who approves, where the data lives, which systems talk to each other, and where the final signature lands. It never appears on a financial statement, yet it decides whether a growth target gets executed in three months or twelve.

2026 made this hard to ignore in Vietnam. The Law on Personal Data Protection took effect on January 1, 2026. Decree 337/2025/ND-CP on electronic labor contracts took effect on July 1, 2026. Companies with flexible architecture adapted in weeks. The rest took a full quarter, and more than a few HR teams kept printing contracts for wet signatures "just to be safe."

Before you lock the 2027 plan, these five questions deserve a meeting of their own.

1. How many handoffs does a critical transaction pass through before it is done?

Pick one real process: a procurement contract, a new employment contract, or an addendum with a distributor. Ask your operations team to draw its actual journey, not the version in the ISO binder.

The drawing usually looks like this. A request starts in email with Contract_Final_v7_revised.docx attached. Legal comments in track changes. A department head approves on a chat app at 11 p.m. The final version is printed, signed by hand, scanned, and someone retypes the details into the ERP. Seven handoffs, four tools, and no step knows exactly what the previous one did.

Every handoff means data gets retyped, a new chance for error, and a gap in accountability. When the 2027 plan calls for twice as many distributors or two new branches, the handoffs do not shrink. The retyping multiplies.

A good answer: the transaction moves through one continuous flow from initiation and approval to signing and archiving, with status visible in real time. The metric to ask for: average time from initiation to final signature, and how many times data is entered manually along the way.

2. If a new regulation lands next month, how long does it take your process to change?

This is the simplest test of architectural flexibility. Ask your CIO and HR Director: "When Decree 337 took effect, how long did it take us to move labor contracts online, and are we done?"

If the answer is "in progress" or "waiting for the software vendor to update," your architecture runs on someone else's roadmap. And regulation will not stop at Decree 337. Electronic documents, personal data, identity standards: new rules will keep arriving, often with less lead time than anyone would like.

Our view: the right question for 2027 is not "are we compliant?" It is "how fast can we comply next time?" Good architecture lets you reconfigure approval flows, templates, and verification steps with drag and drop, instead of opening a new development project every time the law changes.

The metric to ask for: days between a regulation taking effect and the new process running live, and how many steps in that process require a developer.

3. Where does identity and signing data live, and who is accountable for it?

Try a very specific question: where is the ID card scan for last month's new hires stored right now? The answer is often "in the recruiter's inbox," "in a shared Drive folder," or "the admin lead keeps the paper copies." With the Personal Data Protection Law now in force, each of those answers is a risk with a name and a clause number.

A sound operating architecture answers three things. Identity is verified against a trusted source, checked against national data rather than a phone photo. Documents are signed with legally valid digital signatures. Every view, edit, and signature leaves an audit trail.

When an inspector or a partner asks who accessed a file, the answer should take seconds on one screen, not three days of digging through five people's inboxes.

The metric to ask for: the share of records with a complete audit trail, and the number of places personal data is stored outside official systems.

4. Is your 2027 technology budget buying new capability or paying for fragmentation?

Ask finance to split this year's technology spend into two columns. The first is the cost of keeping things running: maintenance, overlapping licenses, patchwork integrations, and staff hours spent on data entry and reconciliation. The second is spend that creates new capability. Many leaders are surprised by how large the first column is.

One easy signal: you are paying for three or four tools that do roughly the same job. Sales uses one e-signature product, admin uses a separate approval tool, legal stores contracts in a third system, and someone still reconciles all of them in Excel at month-end.

A good answer is rarely to replace everything. The practical move is to consolidate identity, approval, signing, and archiving onto one orchestration platform, while keeping ERP and CRM as systems of record.

The metric to ask for: the number of tools with overlapping functions, and total monthly staff hours spent on manual entry and reconciliation.

5. Does your architecture reach beyond your own walls?

Most internal systems were designed for people sitting in an office. Yet the transactions that matter most involve people outside it: customers signing contracts, distributors signing addenda, candidates in another province signing employment contracts, suppliers submitting qualification documents.

If those people still have to visit your office, send documents by courier, or receive a signing link with no identity check, your architecture stops at the firewall. Your 2027 expansion plan, whether it adds regions, channels, or partners, will hit that limit first.

A good answer: external parties verify their identity through eKYC, sign remotely on their phones, and the result flows back into internal systems automatically. The metric to ask for: the share of external transactions completed fully online.

From Questions to Action

None of these questions needs a large consulting engagement. A two-hour session with your CFO, CIO, COO, and HR Director, each bringing one real process to draw on the whiteboard, is usually enough to see where the architecture holds and where it breaks. 

Kyta Platform by FPT IS is built for exactly this layer: the orchestration layer between people and core systems. Kyta eKYC verifies identity with data checks against the Ministry of Public Security. Kyta Signature provides remote digital signatures and electronic contracts certified with the Ceca green tick from the Ministry of Industry and Trade. Kyta ALM digitizes the full agreement lifecycle, from initiation and approval to signing and archiving, on a no-code/low-code platform that connects to the systems you already run. More than 4,500 businesses have chosen Kyta Platform.

Conclusion

The 2027 plan will set the targets. Your operating architecture decides how much effort it takes to hit them. Ask these five questions before the budget is locked, while change is still cheap, not in June when the plan is already halfway down the road.

Contact Kyta Platform: kyta.fpt.com | Hotline: 1900 636 121 (ext. 2) | Email: support.kyta@fpt.com