Yuzool · proof before promises

We use the products on ourselves first.

These are small, honest case studies from building Mac and iPhone apps in public from Japan. The numbers are not inflated and the misses stay in the record.

Start with RankRead the distribution log
01 · RANK ON YUZOOL

Turning Search Console into one weekly decision

We use Rank to choose a Yuzool page, record the baseline, ship one controlled change, and return after 7, 14, and 28 days.

Proof: the live weekly growth log, including the Tinylytics baseline and next experiment.

Read the Rank growth log →

02 · DISPATCH KUN

Turning an App Store release into a mini-launch

Dispatch Kun is treated as a distribution experiment: explain one job, share one link, listen for the language people use, and improve the next release.

Proof: a public launch recap instead of a silent “new app” announcement.

Read the Dispatch recap →

03 · THE MAKER LOOP

Learning distribution without pretending we have an audience

Each page, public reply, and product update is a small test. We track attention, intent, evidence, and revenue, then publish what changed.

Proof: the maker story and the weekly operating loop behind the work.

Read the maker story →

04 · CUSTOMER VOICE

What people say after using the tools

Customer language is more useful than a polished claim. These are the words behind the product decisions, support replies and next screenshots.

Proof: verified testimonials with product context and live examples where available.

Read customer voices →

What this means for customers: you can see the workflow before buying. If a product does not help us finish a real job, it does not deserve a larger promise.