Equity distribution in early-stage startups is a slightly odd subject. Obviously at this point the startup is worth nothing – or less-than-nothing, if expenses are being recorded as debts on the future company – and who wants to argue about percentage points of nothing? Sometimes the whole subject is just ignored.
On the other hand, whatever the addressable market size of the idea at hand, the spectre of founders squabbling over enormous wealth is lurking somewhere in the subconscious of everyone involved, so it is equally possible to go the other way, and invoke complex calculation methods of one kind or another, however irrationally over-fussy.
While complex approaches are arguably better than failing to address the issue at all, a simpler method is more typically adopted: if there are two founders at the beginning, they are usually assumed to have 50% each, if three, 33 1/3%, etc – as in this Seedcamp agreement template.
If they add additional co-founders, there is a re-distribution by agreement, such that the original co-founders see their percentage ownership reduced, to ‘make room’ for the new partner. The process is repeated each time a new equity-holder is added (ignoring such things as special share types – usually considered as over-complicated at early stages).
I consider that there are several problems with this:
Continue reading “Startup Equity Distribution – an incremental approach” →
We’re building a medical app. Of course, Therapy-Smarter isn’t collecting deeply intimate data – just basic contact information, some physiotherapist’s notes, exercise prescriptions and exercise performance data – but nevertheless, medical data is medical data- it’s inherently sensitive, and any company that cares about its reputation needs to take data privacy – and thus data security – very seriously indeed.
So, we’ve been thinking about it fairly hard – but not in a technical way; it’s a specialist domain and we assume that we will need to pay people who know what they are doing to advise us on best practice and then get them to assess our implementation.
No, we’ve been thinking hard about security in terms of business culture, because it seems painfully clear that this is where security weaknesses really come from. That’s right – I’m saying that security weaknesses have much more to do with business culture than they have to do with engineering.
Continue reading “Security as an Overhead isn’t working” →
This is in many ways a companion piece to my previous post – it started out as a version for LinkedIn, but rapidly evolved into something with a different emphasis.
The internet revolution has changed the landscape of our lives, and yet the disruption has only just started. Existing ways of doing business are largely unchanged from the way they were 20 years ago. Hilarious disconnects exist all over, when ultra-slick digital-only processes crash into messy physical transactions.
There is a reason for this. Coders like to code – they like the safe, ordered, complicated-but-not-truly-complex world of programming. And coders are the ones who feel empowered to invent digital businesses. So, of course, the early digital businesses are the ones that can be achieved with purely digital workflows, and don’t require the startup team ever to leave their own world.
Continue reading “Developing a Digital idea without Developers” →
I’ve mentioned before that we’ve used FPro as a type of Rapid Application Development Platform. Building a fully functioning prototype using this high-level (largely graphical) database application has allowed us, as non-coders (albeit with a decent understanding of how a properly architected database should be structured), to develop our therapy-smarter tool in an iterative way, without spending large amounts of money.
Another benefit is that the product we are using remains fully accessible to us at the architecture and data level, and is largely self-documenting. FilemakerPro produces human-readable graphical representations of its database structure as a standard report and the functional scripts are basic-like in their use of real language, and thus easy to follow.
What this means is that, for a team like ours, without coders, the scary step of commissioning native code from people whose work we will ultimately not be able to judge in detail is made much less risky. When we judge that the time is right to take the system to the next level – when we need it to go faster and handle more clients, we will have to get the thing recoded – and this will mean bringing developers in.
For startup teams without coders, this is a terrifying point. How do you find the right person? How do you choose which framework, which language, which platform, which architecture? How can you even begin to judge the recommendations you are hearing? How can you describe the features you want?
Continue reading “Using FilemakerPro as a RAD platform just got more interesting” →
In April I introduced MyPhysioLink – the physiotherapy start-up that I and my co-founder, Cris Costa, have been working on. With the beta launch of the service imminent, we looked long and hard at the name and decided it wasn’t good enough.
So we are now Therapy-Smarter.com. Visit our website to see what we’re up to, and for the latest news on our progress. Physiotherapists can sign up for a free trial.