David Kim

David works on the decisions that come before implementation: which problems are worth automating, what the stack should look like in 18 months, and how to compare vendors without being led by a feature list. He turns ambiguous goals into a sequenced roadmap with costs, dependencies and measurable checkpoints.

He is most useful when a team has many options and limited budget. David runs structured evaluations, brings competing stakeholders to a shared definition of success, and insists on writing down the trade‑offs. Tools are chosen for fit and exit cost as much as for capability, and projects are staged so value lands early rather than at the end.

His strategy work spans content architecture, measurement, channel mix and the organisational changes that make any of it stick. He is a proponent of entity‑driven content structures that help both search engines and AI answer systems understand what a site is about, and he connects those structures to analytics so content decisions are made with evidence.

On the blog, David writes about vendor selection frameworks, KPI selection that resists gaming, budgeting for AI features and the politics of internal adoption. He devotes equal space to risks and to the operational overhead of new capabilities — maintenance, training, documentation — because ignoring those costs is how projects stall six months after launch.

Recently he has guided teams through stack consolidations, helped product marketing leaders plan AI‑assisted content operations, and partnered with finance to reconcile attribution models with revenue reporting. His playbooks are designed to be borrowed and adapted by in‑house teams.

For a representative sample of his approach, read David’s articles on selection criteria, content architecture and measurement on the NexaMarTech blog — they include templates you can use directly in your own planning.