Why bother with a one-pager?
Let's start with why do a one pager. As mentioned earlier, it is often used to get an initial face-to-face meeting and in that sense, you could almost describe it as a combination of a CV and a pitch deck. In fact, much of what I talk about in another post about the pitch deck and my thoughts on how to present it well equally apply to this earlier stage of the process, particularly the Q&A.
A lot has been written about how to write an excellent one pager and there are a couple of references that I do rate. Those are one pagers from an investor perspective and what should be in one and also avoiding some common one pager pitfalls.
Nonetheless, as the title of post says, I am going to focus on how having access to the one pager greatly accelerates the initial phases of the IT Due Diligence process.
Business summary, customer problem, product and/or service and target customers
From an IT Due Diligence perspective, getting early access to the one pager, greatly assists with gaining a rapid overall understanding of the business, the customer problem and the proposed or current solution. In this respect, the business summary, customer problem, product and/or service and the likely target customers sections of the one pager are of particular importance. The business summary sets the scene and helps with a high level introduction to the organisation. The customer problem, product/service and the likely/target customer section can be reviewed together as they are closely linked. Taken all together this information allows me to form a very early view of the sort of technology choices might work in this proposal. if there is a product already in place and it is serving customers then the view is about how well/easily will the product and technology scale to cope with the proposed demand.
The next area to look at is the team. The management team, key players and advisors as well as numbers of employees are the key information in this respect. At this stage, I am looking to understand what sort of technical capability might reside within the team and how that confirms or changes the view of potential technology choices formed in the previous section.
Business model and financials
I now look at the business model together with the financials, with an eye to affordability of the technology. Clearly this depends on whether there is an existing implementation where the technology has already been chosen or it is at "build stage where the technology decisions still need to be made.
Sales and marketing strategy
Finally, the sales and marketing strategy can be helpful in assessing the technology, as the go to market strategy needs to match the (potential) product and how it might scale/be scaled.
At the end of reviewing the one pager, I generally have a good view as to where to start with my questions, when I first meet the technology team, as well as no longer needing a high level introduction to the business - all of which saves precious time for everyone.
As you can imagine, this is an enormous area and whilst I have some experience, I would in no way consider myself an expert. Nonetheless, I would be delighted to see if I could put you in touch with someone, should you be looking for some advice and guidance in this area.