I have one thing for you to consider as far as representation of the solution. I believe that it is highly important that the solution becomes a cycle, rather than a straight line series of steps. You helpe to solve the knowledge issue, uncover customer behavior utilizing technology which then helps you to solve OR creates more knowledge that will help you to uncover customer behavior and so on and so forth. Graphical representation are a strong idea. I think what you have here is great in describing the problems that you solve and what parts of your business solves them, but there might be a need for a stronger representation of how those problems get solved and thus perpetually benefit the company in terms of an ongoing cycle. Additionally, the more that you can prove that your consultation is involved in a cyclical business model, the more dependent your client will become of you. If it's just a straight line, what's to keep someone from dumping you after step three?

I like the recycle idea alot. Of course that is part of the idea, but for now I have been unable to add it into the diagram without making it overly complicated. Perhaps another dimension?

I Agree with the Cyclic approach Stu is describing.

The other dimension you seek is a constant refinement of business processes based on the insight you would provide for companies in their data (the cycle). If at some point in time such companies can aqcuire the hardware, more qualified personnel it also means they acquire more data simply because their customer base grows as they are making the right decisions on their data in terms of marketing, product development and sales strategies. If GishTeq keeps providing added value in this cycle such a company would invest in its core business. Not necceserily in acquiring personnel to do data analysis, as strengthening core business is the most vital part in their business processes. There ara a lot of study cases of big companies where for example Human Resource management stays outsourced such as payroll, retirement and benefit plans and they keep focussed on their core business. Might GishTeq run into a corporation that chooses to get people inhouse instead of choosing the outsourced strategy over time then all is not lost because you will have some very good business cases on your website in your portfolio.

Right on Sjef. Indeed, a model is by definition an approximation of the situation and is not meant to be a completely exhaustive description of every possible aspect which may or may not come into play in the (near) future. Otherwise, I would end up with something way too complicated for the customer. The poor guy would stare with large open eyes at the huge diagram I had plastered across the length of his meeting room wall and shake his head in confusion. I want to attract customers and NOT scare them away. However, using the creative power of recycling would be an advantage, something akin to reinvigorating the business processes and keeping them alive. The model should be extended to take the energy of the output and feed it back as part of the input, e.g. a regulating process.

Sure, you should just take the first sentence, not the whole thing in a diagram. (seriously)

But remember, chaos in data might result in a couple of questions but the first cycle of "metrics" performed by GishTeq will result in even more questions.

If a customer gets scared of something that is pretty generic such as improving core business than I don't forsee a long term relationship.

i dont know what will be my plans about biafra nigeria