top of page

Why was Oyster born?

Concentrate on what you do best

Building one's own is tough

  • To commission a bespoke system of this nature starts at low 6 figures for a basic shell. That’s just to start… 

  • The complexity of architecturing such a system is complex and usually underestimated

  • The demands being placed on the system and the brief given to those building your system may evolve dramatically during the project’s lifecycle. 

Outsourcing development too

  • "Lost in translation" (what you mean and what a developer understands) may lead to “red-herrings” on the development road or discovery that the infra-structure cannot accommodate changes you discover you need due to it not being anticipated in the architecture at the start

  • This means much time spent, frustration and, of course, money…good developers are very, very expensive. 

  • If one is not able to focus 100% of time on project-managing the project the frequency and cost of these “red-herrings” will escalate. 

Avoid spiralling uncontrollable costs
Avoid red-herrings in fields that you are not familiar

Spiraling costs versus missed targets

  • Usually these projects dramatically overshoot the allocated timeframe, estimates and therefore budget 

  • Re-engineering existing“Off-the-shelf” packages is rarely successful in creating a system that meets 100% of requirements. Will the final system be fit for purpose?  You may spend more time and money trying to make it do something it is not designed for. 

  • Change one element and the knock-on effects may be numerous and not obvious/ only discovered later

  • The bespoke approach can be hit or miss if you don't have the time. It CAN give you what you are looking for but at what cost and what if it goes wrong? 

FACT

Statistically 90% of expenditure and time taken is usually on the final 10% of implementation of such projects. Many such projects are shelved due to the final result not meeting ALL expectations(usually down to architectural errors early on preventing accommodation of later changes / evolution of requirements) or because of the escalating costs resultant from the additional developer time (not to be underestimated how much developers cost).

bottom of page