DKBinnovative

10/29/2026

The call usually starts with the software. The practice management system is slow. The tax software crashed in the last week of February. Is it time to switch platforms?

Almost always, no.

Those products are mature and the firm chose them for good reasons. What's wrong is that nobody owns how they fit together. Your tax software vendor supports tax software. Microsoft supports Microsoft. Your document system vendor supports the document system. Every one of them is doing their job, and every one of them can honestly tell you the problem is somewhere else.

That's the gap firms feel. Not a bad product — unclaimed space between good ones, plus the handful of things nobody has looked at in years because they were never anyone's to look at.

Not better software. The same software, owned properly.
We rarely replace the stack a firm already paid for. We take ownership of it.

​​https://na2.hubs.ly/H089h5n0

10/27/2026

Every MSP supports your standard tools. Far fewer will touch the software your firm actually runs on.

Practice management. Tax software. Portfolio accounting. When one breaks, you learn fast which kind of provider you hired, because the answer is either a fix or a forward.

Ask a generalist about an application failure and you will usually hear that it's the vendor's responsibility. That is technically true. It is also operationally useless when a return is due and five people can't work. "That's a vendor issue" closes the ticket. It doesn't close the problem.
Owning the layer means holding real competence in the application and working the problem with the vendor instead of handing it to them, with updates scheduled around your busy season rather than through it.

Looking for a partner who works with your vendors for proactive management? Contact us now! https://na2.hubs.ly/H089h290

10/26/2026

Every guide to the professional firm tech stack is written by someone selling one piece of it. This one is written by the people who get called when the pieces stop talking to each other.

Seven layers, in the order of what everything else depends on: identity, email, document management, the line-of-business application, backup and recovery, endpoint and network, and monitoring and advisory.
The document system has to authenticate against something. The billing platform has to be backed up in a way you can actually restore. The email tenant has to be the same tenant the practice management tool trusts. Most of what goes wrong in a real firm happens in the seams, and nobody selling a product writes about the seams.

What we actually find in each layer when we take a stack over:

A professional firm tech stack, layer by layer, with what we actually find when we take one over. Real findings from law, CPA and wealth management engagements.

10/23/2026

🚀 Happy 5-year DKB-iversary, Jun!

Five years ago, Jun joined DKBinnovative, and he's been a huge part of our mission ever since. As our vCTO Team Lead, he helps our clients plan their tech future and keeps our team on course. Thank you for your leadership, your expertise, and everything you bring to DKB, Jun. Join us in congratulating Jun!

10/22/2026

Your encrypted client data could be stolen today and read in 2033. Nobody would notice until it was too late.

That's the "harvest now, decrypt later" threat. For law firms, CPA firms and investment firms, it is a present-day risk rather than a future one:

- Attorney-client privilege never expires
- Social Security numbers and tax records never get reissued
- RIA client data has to stay protected for decades

NIST is phasing out today's vulnerable encryption after 2030, and firms that hold long-lived confidential data are already inside that window.
Our new guide explains what post-quantum readiness means for DFW professional firms, why crypto-agility matters more than any single algorithm, and six practical steps to take this year. None of them involve buying a "quantum" product.

Read the full guide: https://na2.hubs.ly/H089gzN0

Post-quantum readiness matters early for firms whose confidentiality duty never expires. What harvest now decrypt later means for privileged data.

10/21/2026

The tickets that sit longest at a multi-office firm aren't the hard ones. They're the ones that belong to nobody.

Each office has an idea of who handles IT. Neither idea covers the space between them. So the printer in Frisco gets fixed same day. The laptop in Southlake gets fixed same day. And the thing that spans both — the shared drive only half the firm can reach, the client file that exists in two versions, the sign-in that works in one office and not the other — sits for a week while two people each assume it belongs to the other.

That space between offices is where most of the multi-office IT problems we get called about actually live. Not in either environment. In the seam.
The fix isn't more people. It's naming an owner for the seam in writing, before it matters.

Most firms find out they never did that about four months after the second office opens.

https://na2.hubs.ly/H089grF0

10/20/2026

Applications are one of the loudest problem after a merger, so they often get solved first. But an application consolidated on top of two identity systems has to be rebuilt once identity is finally fixed - new tenant, new permissions, new migration, this time with live client data in it. You pay for the same project twice, and the second one is worse.

- Centralization has a fixed order, and it isn't negotiable.
- Identity. One directory, one set of credentials, conditional access applied the same way in both offices. Everything above it inherits from here.
- Data. One repository, migrated with permissions intact and a record of what moved.
- Policy. Retention, legal hold, device standards. Written once, applied to both offices.
- Applications. Practice management, time and billing, portfolio accounting. Now they land on something that won't move under them.
- Network. It matters, but it is the easiest piece to change and the least likely to cause a compliance problem. Last for a reason.

https://na2.hubs.ly/H089gdZ0

10/19/2026

Opening a second office or closing on a merger? Your IT problems start about four months after the deal.

Across Dallas-Fort Worth, law firms, CPA firms and RIAs are consolidating fast. Most of them run into the same issues:

- The same client file exists in two places, with two version histories
- The acquired firm still has open admin access
- A WISP or Reg S-P plan that only covers one office

Our new guide covers multi-office IT for professional firms in Frisco, Plano and Irving. It explains what breaks when a second office opens, the right order to centralize (identity → data → policy → apps → network), and a pre-close checklist to work through while you still have negotiating leverage.

📖 Read it here: https://na2.hubs.ly/H089fXm0

10/17/2026

You probably don't need a full-time CISO. But you do need the expertise of one.

In our last video, Dusty shared tips to protect your users today. Good habits are only the start, though. Protecting your firm from sophisticated attacks takes a mature security program, built and managed over time.

That's Dusty's role as a vCISO at DKBinnovative:
- Senior security leadership without a full-time executive hire
- A security program that matures over time, not a one-time checklist
- Protection for how you operate without slowing down how you work.

If October showed you gaps nobody owns, let's talk: https://na2.hubs.ly/H08ny5h0

10/14/2026

Most breaches don't start with super advanced AI. They start with missing basic protections. Dusty Burris, our vCISO, shares 3 quick upgrades for Cybersecurity Awareness Month:

- Passphrases over passwords. They're harder to crack and easier to remember.
- Use a password manager. No more spreadsheets and no more reusing passwords. You get a strong, unique password on every site, filled in automatically.
- Switch to passkeys. Attackers can now get around MFA by stealing your login session. Passkeys are phishing-resistant, and logging in is faster.

Get the full Cybersecurity Awareness Month checklist: https://na2.hubs.ly/H08ny5L0