About
Seiko Yamaguchi
Founder, Consilegy LLC / Revenue Architect
I design B2B revenue structures, implement them, and see them through to adoption on the ground. The work is to take marketing, sales, and customer success operating in silos, and rebuild them into a single revenue process.
I am not a reseller for any single tool, so I choose the design that fits the business, whether that runs on Salesforce, HubSpot, or kintone. The engagement does not stop at upstream design; it assumes implementation and operational adoption through to the end.
What I work on
- Revenue Architecture design
- RevOps, sales process, and KPI design
- HubSpot / Salesforce / kintone implementation and migration
- MA / SFA / CRM data design and data quality
- Japan market entry for global SaaS (Japan GTM)
- Post-implementation adoption and enablement
About this edition
What is written here comes from real engagements: what was chosen, what worked, and what did not. Rounded to a level that respects confidentiality, but recorded together with the reasoning behind each decision.
I have decided not to write generalities. Sentences anyone could write, like "sales and marketing alignment is important," do not go here. There is no point placing content you can already read elsewhere.
The definitions and the framework itself live on the corporate site, in Japan Market GTM and Messaging and the broader revenue architecture work. This edition is the record of how that framework did, or did not, function in the field.
How I handle numbers
When an article cites a number, it always states three things: who ran the study, in what year, and the sample size. Numbers whose source cannot be traced, or that circulate in a form different from the original, are not used.
This field carries more than a few figures that keep getting quoted with murky provenance. For example, "the average B2B buying group is 5.4 people" is a value from a study CEB ran on US companies, not Japanese data. Points like these are flagged in the article itself.