university
Open Kite
All stories
First customers · Reported story

Stripe's early lesson: help an interested customer actually start

The Collison installation was a small, direct response to a familiar gap between agreeing to try a product and using it.

A developer helping an interested business owner get started on a laptop.

Agreement is only one part of getting started#

Someone can want to try an offer and still be unable to make progress. Setup, uncertainty, missing inputs and a busy day can sit between interest and first use.

In Paul Graham's account of early startup work, the Collison brothers helped people who agreed to try Stripe get set up on the spot. The approach became known at YC as the Collison installation. The reported behaviour is specific: helping an interested early user begin. It does not establish a universal effect on purchases.

For another business, the useful question is where an interested person gets stuck and what appropriate help would remove that obstacle.

Find the first useful outcome#

Define what a customer should be able to do after beginning. A software tool might support one real workflow. A consultancy might provide a clear assessment. A service provider might confirm scope and schedule an agreed first job.

List every dependency before that outcome: inputs, access, a responsible person, a decision and instructions. Ask which dependency causes uncertainty for a new customer. A signup count will not reveal all of this.

Observe the customer's actual attempt with their permission. Let them describe the confusing part rather than instructing them to say the process is easy. Use authorised information and avoid recording private screens for public proof.

Offer help that belongs within your scope#

Good setup help is deliberate. Explain what the customer controls, what your team will do and what access is genuinely required. Never treat interest as permission to take control of a device, accept terms or change an account.

Prepare a first-use checklist, the smallest workable input and a named support owner. A technical provider may need a scoped assessment before implementation. An agency may need approved source material before it can deliver an asset. A founder may need to explain the one task the prototype supports.

Use the pilot guide when the engagement needs an explicit value test and commercial agreement.

Learn what can be made repeatable#

If the same obstacle appears repeatedly, improve the product, instructions or handoff. Keep the effort visible. Founder help that takes several hours per account creates a different capacity requirement from a short orientation.

A growing business needs to decide which help is included, which requires a separate scope and which can be made easier for the customer to complete independently. Do not remove a necessary human decision simply because a process looks automatable.

Kite can help create the qualified conversation. Your offer still needs a usable next step after the Introduction. The sales-and-delivery capacity guide helps check whether the support behind that next step can grow with the demand.

Sources behind this story

Primary accounts and industry guidance inform the facts. The discussion and recommendations are Kite University's editorial analysis.

Read this story with your agent
Your next conversation

Give your business goal
a place to start.

Kite is an introductions platform. It gets you into phone or video meetings with qualified people who have a reason to do business with you.

Explore your goal with Kite

Put the idea to work.

How to turn customer interest into a useful paid pilotPlaybook · 5 minHow to get your first clients for a service businessPlaybook · 5 minHow to grow sales and delivery capacity togetherPlaybook · 5 min