Proppy is a tool for freelancers and small agencies needing to send proposals to clients. I had the real pleasure of working with the guys at We Are Wizards to bring the project to life, helping them recognise the issues they needed to address, as well as designing the interface and a temporary brand.
In order to work out the most important factors for Proppy to consider, I worked closely with the team to investigate the common issues around creating proposals:
We discovered the following recurring problems:
Winning a project requires a huge amount of time and effort. Competition is always high and although you’re confident that you have the best proposal on offer, the way in which you present yourself and your work matters the same or more than the actual work you’re pitching.
Therefore, a tool that cuts the time spent trying to convince someone that you’re amazing — time that you’d prefer to spend doing the actual job — would be essential to freelancers and small businesses.
Most of the users I interviewed would create fairly standard documents to send externally. To create better looking proposals, they usually need the help of designer. But what if Proppy was easy enough for anyone to use while still delivering visual impact? Proppy’s key idea was to allow people to deliver the wow effect, without the traditional skills required.
…unless it sits somewhere in the cloud. Even then, how can you easily separate the conversations you have internally with your team, and the discussions you have with your client?
Many people send quotes to potential clients by email, and use other tools depending on how complex is the proposal. I wanted to figure a solution to get all of this data in one place. I also started thinking how cool and useful it would be to access meaningful data like ‘Proposals Won/Proposals Lost’ during any given year. This would allow people to analyse their performances to improve for future work.
I created a list of features that would solve one or more of the problems above, and sorted them by priority.
‘What are the differences between the editorial interface and the one seen by clients?’
I decided on three key stages:
‘What level of customisation would freelancers and companies want for their proposals?’
I had to ensure that non-designers are able to create good looking proposals. For this reason, and because decision making is time consuming, I decided to limit the number of style choices and locked the editor to one particular design, albeit a freaking good one. There was one colour scheme, a simple font option, and nothing too unusual in between. I then provided users the freedom to add their brand on top of the base layer, which is why I added customisable covers and logos.
The design principle behind the editor’s interface is to look as minimal and clean as possible so that whoever is creating the proposal can focus on the work without getting distracted or bogged down by other factors.
This is what the current version looks like:
Quite early on, I considered an import function for proposals; parts that don’t change so often, like an About section, a Team section, or a Case Study section. How great would it be to be able to quickly and easily import only the Case Studies relevant to a certain project?
After finishing work on a proposal, you can preview the whole document to see it through the eyes of the client.
I realised that proposals often share common structures and that when starting a new one, people often duplicate an old one before changing the contents.
I also wanted a search function that was smart and effortless to use, capable of filtering proposals by client, tags, project name etc. I experimented with templates and anything else that could make the process as easy and seamless as possible.
This is the final dashboard design:
Proppy is currently undergoing a heavy series of tests, and therefore we’re constantly improving it. It doesn’t yet have a finalised brand image, which is something I will be working on very soon.