Kawasaki was an early Apple evangelist and later a venture investor, and this is the revised edition of his practical guide to starting an organisation. It is written as a set of instructions organised by activity rather than as an argument.
The chapters cover starting, which he frames around making meaning rather than making money and around answering what the organisation makes possible; launching, including the advice to ship and then test rather than perfect; leading; bootstrapping, with specific cash management instructions; pitching, including his ten slide rule with a twenty minute limit and thirty point type; writing a business plan, which he treats as secondary to the pitch; recruiting; raising money; partnering; branding; rainmaking; evangelising; socialising, covering online presence; and enduring.
His most cited specific material is the pitch structure, which specifies the ten slides and their order, and the argument that a plan exists to force the thinking rather than to be read. He includes material on crowdfunding, on social media and on self-publishing that the first edition predated.
The book is a compilation of tactical advice and offers no framework. It is written in a breezy register with frequent lists, and the substance per page is low. The specific advice dates quickly, particularly around platforms and fundraising mechanics. The pitch structure and the cash management instructions are what practitioners actually use, and both can be extracted quickly.
First-time founders who want tactical instructions, particularly the pitch structure, extracted quickly rather than read through.
Chief evangelist at Canva; earlier Apple's Macintosh evangelist and a co-founder of Garage Technology Ventures.
The Art of the Start breaks early-company work into concrete tasks - pitching, positioning, recruiting, bootstrapping, partnering - for founders with no prior company behind them. The Macintosh Way and Selling the Dream document how Apple built developer and customer evangelism into a product launch, which is where the modern practice of developer relations comes from.
Chosen by shared topics, the entries that hold them, and the people who recommended both.


