Frequently Asked Questions

Jozu builds revenue infrastructure, which means the written process, the claims, and the review discipline that decide how a sales organization runs every deal. The work links what a company has built to the problems buyers are willing to pay to solve, and it is designed to keep operating inside the daily workflow once it is in place.

Companies selling complex products into enterprise buying groups, where a purchase involves several approvers, a long cycle, and a procurement process. It applies most directly where deal sizes are smaller than the problem the product solves, and where the pattern repeats across the team.

Revenue infrastructure is the part of a sales organization that persists when individual people change. It includes the written discovery sequence, the tested claims, the follow-up documents, the stakeholder map, and the review standard a manager applies to a deal. Capability that lives only in one person's judgment leaves when that person does.

Training changes what people know. Process changes what people do, and only what people do compounds. Jozu builds the process and the artifacts, then teaches the team to operate them, so the standard survives turnover and new hires inherit a working system.

It begins with a conversation about current deals. Looking at live opportunities and the written artifacts attached to them shows where deal size is being set and where the process is silent. That produces a diagnosis before any commitment is made.

Access to sales artifacts from real deals, which means the proposals, the follow-up emails, and the written notes from buyer conversations. Time with the people who sell, and time with whoever reviews their deals. The diagnosis depends on real material from live opportunities.

Your team sells. Jozu builds the system they sell with, works the live deals alongside them, and sets the review standard their managers apply. A process written by someone outside the team and delivered as a document does not change behavior.

Pricing is set on a call, once the scope of the problem is clear. The shape of the work changes with the size of the sales organization and the state of what is already written down, so a number quoted before that conversation would be guesswork. Please get in touch and we will talk it through.

That is the design requirement. Everything is written down, embedded in the tools the team already opens every day, and built into the standard a manager applies in a deal review. The measure of the work is whether the discipline holds when nobody is watching it.

The Plan Letter is the written follow-up that carries the agreed steps between the current conversation and the date the buyer needs the problem solved. It names who does what, carries the claims that matter to each approver, and gives the buying group a document they can circulate internally without rewriting it.

A Power Message is a single written claim linking one capability the seller holds to one problem that costs the buyer money. It has to pass three tests: a competitor cannot say the same sentence word for word, the seller can prove it, and it is attached to a cost the buyer has already described. Read more.

The Jozu Power Score is an objective grade of a sales team's ability to reframe the pricing conversation. The Jozu Revenue Engine reads a team's own sales artifacts and scores whether the seller accepted the buyer's narrow unit frame or expanded it to economic consequence. Read more.

Pain Amplification is discovery that uncovers what the buyer's current situation is costing them. The seller asks questions that follow the problem past the department that feels it, to the operational consequences and then to the annual figure, so the buying decision gets sized against the cost of leaving the problem in place.

Surround sound means reaching every person who can stop an enterprise purchase, before the decision is made, and giving each of them a reason to proceed that is attached to the cost that person carries. A purchase carried by one contact depends on that person staying in their role and arguing the case accurately when the seller is absent. Read more.

Buyers describe their problem at the point where they feel it, which is usually the narrowest version of it. Following the problem downstream means asking what happens next at each stage, through the operational impact and the effect on the buyer's own customers, until the conversation reaches an annual cost. That figure sizes the purchase. Read more.

Yes. It is a focus of the practice. A Japanese company entering the United States usually has a product that works and a sales motion built for a different buying process, and the gap between the two is where deals are lost. The work addresses the sequence a US enterprise purchase requires. Read more.

Yes. This site is published in English and Japanese, and the language used for engagement documents is agreed at the start of the work.

The number of people who can refuse the purchase, and how early they need to be involved. A US enterprise buying group commonly includes a budget holder, a technical evaluator, the manager whose team will use the system, a security reviewer, and procurement. Each can halt the purchase, and each is measured on something different.