We Take Bespoke To A New Methodology

We take bespoke to a new methodology by changing the normal industry model by starting with our off the shelf software, or OpenSource software, or a customer base code and enhance it to a completion. Rarely, although possible, do we actually start form scratch. We have found that in most case the customer needs speed with the delivery and starting from scratch tends to press the costs and the time beyond acceptance. So the model improves in time especially quick with cut down requirements, keeping the delivery simple, starting from a point as far in as possible, and then extending it downwards into the development instead of trying to do everything at once.

Using ‘smart architecture’ methods we, instead of going vertically, go only horizontally for the first deployment, putting in function across the horizontal instead of adding depth of features. We amen sure it is integrated instead of creating a huge developed middleware before launch. What this does is dramatically reduce, through an agile process, the time to market for any given product within the bespoke model.

A key element of this phase is to identify all key stakeholders and engage with them early in the outsourcing process. This is especially critical where those stakeholders have little or no experience of outsourcing. Expectations set in this initial phase will be difficult to change later in the process.


We have to start with consideration on all key aspects of the software development lifecycle, particularly with regard to:

  • The overall objectives for the products, which should be more than simple, short term cost reduction

  • The financial benefits which can be delivered by an appropriate CFS

  • The costs which will need to be incurred in order to deliver the first product to the customer

  • The risks which must be mitigated in order to ensure a successful outcome

  • The degree of change required, as minimum as possible, by both business and IT functions in order to ensure that the product is successful for the initial release and of course the later ones

  • Once the initial business drivers are understood, and the method agreed, a high-level business case needs to be created. It is always too tempting for a customer to over do the requirements for delivery, in Etheria we place the initial build into contract, so there cannot be too much creep and therefore guarantee the customer delivery even if the customer is his own worst enemy.

    This model seems to mitigate a lot of risk and cost to companies within the bespoke model. As we start from a good entry point, hopefully 80% in, time, cost and proven viability are already controlled and accepted. We believe this is the future of the bespoke model.