We are a small startup that creates simple, concise software. We strive to create software that enables, rather than disables, users. We believe that the future of application development is split between the web and mobile devices (more often than not a combination of the two). The applications of the future will need to be web based, accessible from any browser, and fully integrated with mobile devices.
Our designers can do copywriting, our developers know how to design and this in turn means you get more for your money. Everyone on our team will communicate with you. We have no specialist coders hiding in a dark room. We firmly believe that if our staff are going to develop something for you, they should also be able to communicate with you too.
We are not a big company and we are proud of it. As a small company we enjoy less formality, less bureaucracy, higher levels of creativity and freedom. Being small allows us to get closer to your needs and allows for a more direct and personal relationship. Some of the reasons we hope you will want to do business with us.
We feel that by ditching the large company formalities the process becomes more efficient, fluid, open and honest. This leads to a much greater flow of ideas and creativity – one of the key advantages of staying small.
We believe that software should have a vision and an opinion, it should never sit in the middle. This opinion should be one of the top priorities. This way the software has an attitude and takes a position that people can clearly see.
We believe in building what is necessary, what makes people productive, without bogging them down with minute detail. We believe it is these details that holds up software, stops real world feedback and eventually makes software bloated and less flexible. More features do not equal a better product.
Improving care for critically ill patients.
Instant z-scores and centiles for the many cardiac and paediatric measurements that are made in normal clinical practice.
Caseleaf is used by anaesthetists worldwide to provide concise and effective case management.
Create, sign and send talent releases directly from your mobile device. Simple, effective model and property releases.
Infections is useful for doctors, nurses, pharmacists and anyone who needs antimicrobial prescribing guidance in their pocket.
The most comprehensive handheld cot side tool for clinicians working in neonatal intensive care.
Paediatric Emergency Drugs
For nurses, doctors, ambulance crew and everyone who needs key paediatric drug data in their pocket.
A practical and current paediatric medicines formulary, used at a leading UK Children's Hospital.
An instant guide to valve in valve procedures for clinicians.
An instant guide to valve in valve procedures for clinicians.
We provide a project development service from design through to implementation for Web, iOS and Android.
Software does not get released on time, on budget and in scope. In the rare occasions that it does happen, it is often to the detriment of quality. We don’t follow this approach.
We don’t expect to get it right first time, so we get an iteration in front of your users as soon as possible.
Release, get feedback, then go back and iterate again. The advantage of rapidly iterating is that the feedback is truthful and is a more sound basis to develop against. We have also found that people find it difficult to imagine how an application will work without seeing a working version. Humans respond better to real life, rather than a set of imaginary mockups or worse still a long specification document. Getting an application out into the real world gives real world responses. Release. Listen. Revise. Repeat.
We place a strong emphasis on real world testing, as the feedback from this is invaluable. Testing done in too formal a manner only gives a partial picture. We have found that allowing users to do real world testing gives much better feedback. We also apply this to the testing we do ourselves during the build phases. It also means that your users see their feedback and opinions being actively taken into account. This has the added benefit of building momentum and motivation with your staff.
We believe that any estimate over a few weeks is fantasy. You have no idea what is going to happen in the future. As a result we keep timeframes small and manageable. Tasks are broken down into hours, rather than days. Each task is worked on one step at a time. Any problem that is too big, should always be broken down continuously until it is manageable and digestible.
When building an application, people request many features. But we believe that it should be a priority to consider whether they actually matter or not. Most just don’t. We will always ask if they are really essential, do they really matter? If they don’t we think you should leave them out. The best applications are not the ones that try to answer every possible permutation, they are the ones that can determine which features actually matter or not. By doing this, the productivity on the features critical to the success of the application go through the roof. From experience we have noticed that the most wasted time is spent on feature sets that just do not matter. Cut this out and your application will benefit exponentially.
So how do we go from an idea to releasing something of real value?
Brainstorm - First we establish the ideas. What does this product do? What are the your needs? What needs to be there for the application to be useful? What vision does this product have? What is the core functionality?
Sketch - Next we build quick, cheap and easily talked to sketches. At this stage we are simply trying to get all the ideas out of your head and onto paper. The primary goal is to take the idea out of your head so we can start to create a rough interface.
Prototype - We then use these sketches to build static html / mobile versions of the application. The aim to get something that looks real so that people can talk to it, discuss it and review it. In our experience users respond far better to a real set of screens, rather than long documents. No serious coding yet, just a prototype of your product. Implementation comes afterwards.
Code - When we have a consensus on the prototype, we start coding. Plumbing it in. However we stay flexible. If something turns out to be wrong once the code is in place, we are always prepared to refactor. You should expect multiple iterations of this stage.
We feel that our approach has three key benefits:
It is better to release a product of the highest quality, on time and on budget, than a product full of scope creep and poor quality.
If you would like to discuss our products or services in more detail, please enter your details and any questions you may have below.