Working with founders: how we handle a business that changes every month
How a digital partnership works while the business is still being figured out: small steps and foundations that survive pivots.
The short answer
A founder’s business changes every month, sometimes every week: the offering shifts, the customer turns out to be someone else, the pricing changes, a pivot happens. Digital work for a business like that must be built to change. Small releases rather than big ones. Foundations that survive a pivot: a fast site on structured content, a design system, accounts in the company’s name, a pipeline, none of which depend on the current plan. Features kept minimal until the business proves it needs them, and faked with a manual process where that will do. The partner’s value is judgement about what to build now, what to fake and what to leave, and the willingness to say not yet. Ownership matters more for founders, not less, because investors, co-founders and successors will ask what the company actually owns.
What changes and what stays
| Changes monthly | Stays through pivots | The partner’s approach |
|---|---|---|
| The offering and its words | The site’s structure and design system | Content in structured fields; copy changed in an hour |
| The customer | The measurement setup | Analytics and forms that report by source and segment |
| Pricing and packaging | The pipeline and hosting | Prices in content, not code; releases in minutes |
| Features customers want | Accounts and ownership | Company name on everything from day one |
| The plan | The weekly rhythm | Short list, written decisions, small releases |
| The product idea | The back end, if built minimal | Build the smallest data model that holds what is known |
How we work with founders
- Foundations in week one: a fast site on structured content with a design system, in the company’s accounts, with a pipeline and monitoring.
- Weekly rhythm: a short list, a call, written decisions, previews approved on a phone.
- Small releases, several a week if needed, through the same checks every time.
- Fake before building: manual processes behind simple fronts until volume or pain justifies software.
- Measure from the start: source, conversion, segment, so pivots are informed.
- Say not yet to features the plan has not earned, with the condition that would change the answer.
- Keep ownership clean: repository, domain, hosting, services, all in the company’s name, documented for the next person.
Why ownership matters more, not less
Investors ask what the company owns. Co-founders ask who holds the keys. Successors, and founders who move on, need to hand over. A founder-stage company with its domain on a personal card, its code in a freelancer’s account and its hosting in an agency’s name has a problem in every due diligence and every departure. Everything in the company’s name from day one costs nothing and answers the question before it is asked.
What this means for you
If you are a founder, expect a partner who builds foundations that survive your pivots, works on a weekly rhythm with small releases through real checks, fakes before building, measures from day one, keeps everything in your company’s name and tells you not yet when the plan has not earned a feature. The business will change every month; the digital work should be built so that this is cheap.
Frequently asked questions
How can you plan digital work for a business that keeps changing?
By not planning far: a weekly rhythm, a short list, small releases, and foundations that do not depend on the current plan. A fast site on structured content, a design system, accounts in the company's name, a pipeline. Those survive any pivot. Features built for a specific plan are kept minimal until the plan proves itself, and faked where a manual process will do.
Should a founder build a product or a website first?
Usually a website that sells the thing and a manual process behind it, before software that automates the process. The website tests whether anyone wants it; the manual process reveals what the software should do. Building the product first builds the most expensive thing on the least evidence, which is the founder's most common and costly mistake.
What if we need to move fast and skip the checks?
Moving fast is small releases through the same checks, not big releases without them. The checks take minutes and prevent the outage that costs a week. Where speed genuinely conflicts with scope, the answer is a smaller release on the date, not a larger one untested. A partner who lets a founder skip the checks is not helping them move fast; they are lending them a problem.