All field notes

Leadership · Retrospective

From partner to advisor: what I could still do for Sprintla after stepping back

A printer with one sheet coming out, and a chair with a blue cushion set slightly back from it.
Concept illustration · AI-generated

In 2016 I co-founded Sprintla (Sprint Tech) and built its product. The idea was that a student should be able to prepare a document on their own phone or laptop, check it, and send it to a print shop, instead of waiting for a turn at the shop's PC. I built the cloud-printing workflow behind it: upload and preview on the student's own device, conversion of Word and PowerPoint files on the server alongside PDFs, and integration with the shops' printers, so that pending jobs started automatically once a shop opened and its printer was switched on.

I was a partner in 2016 and 2017. After that I stayed on as a technology advisor until 2019, while my own work moved to city data at Hexon Data and then to a public blockchain at Trivechain. The move from partner to advisor changed what I was for, and it is a change I have been thinking about this month: what someone who helped start a company can still do for it, and what they should leave alone.

What the builder still knows

Code records what a system does. It rarely records why it was shaped that way, and the why is what a builder carries out of the door.

Take the printer integration. A new engineer reading it would see pending jobs wait and then start on their own once a shop's printer is running. What they might not see is the service that behaviour provides: a student can send a document after the shop has closed, and it starts printing when the shop opens and switches its printer on, without waiting for anyone at the shop's PC. Or take conversion on the server. A reader sees Word and PowerPoint files being converted before printing. One thing that does is make the document a printer receives independent of whatever office software the shop's computer has. That fits the purpose of the whole product, which was to reduce students' dependence on that computer.

Changing either of those without knowing why risks breaking the thing the product was for. That is the first thing an advisor who built the system can offer: answers to "why is it like this?", given quickly, when asked.

What an advisor can still do

Beyond history, I think a technical advisor to a company they helped start can usefully do three things.

  • Review a decision before it is made. Not to approve it, but to set out the options and what each one costs, so the people deciding see the trade-offs a builder would see.
  • Name the risks that are hard to see from inside. A team close to its deadlines may not notice that a convenience has become a dependency. Someone a step away sometimes can.
  • Say when a problem is not technical. This is the least comfortable one, and often the most useful.

The problems code cannot solve

Sprintla's product worked. Its hard problems were demand density and shop distribution: enough students close enough to participating shops, and enough shops willing to take part. Neither is solved by better software.

A builder who becomes an advisor is tempted to answer every problem with the thing they know how to build. A faster upload or a better preview is a real improvement, but it does not put another shop on the map. When the constraint is commercial, the most useful thing a technical advisor can say is that it is commercial, and then stay out of the way of the people working on it.

What belongs to the people running it

Stepping back means some decisions are no longer yours, even when you have an opinion about them. Product priorities, which shops and campuses to pursue, how to price, who to hire and how the team works all belong to the people accountable for the result. So does speaking for the company.

An advisor's suggestions can carry the weight of the person who built the system without carrying any of the consequences. I think the fair way to handle that imbalance is to advise in writing, give the reasons, and accept no as an answer. If a suggestion is right, the reasons will still be there when the team is ready for it.

There is a practical side as well. When responsibility moves, the accounts, credentials and documentation should move with it. An advisor who still holds the only copy of something the company depends on has not really stepped back.

Partner to advisor

The change from partner to advisor is a handover of authority while some knowledge stays in reserve. The advisor's job is to make that knowledge available on the company's terms, when it is wanted, and to accept that the decisions it informs now belong to someone else.