My methods

I am able to use different development methodologies, these being:

It is critical that I understand what you need first. I will then tell you if I can help, or I refer you elsewhere. I believe that this is the way to build long standing customer relationships. It is also the way to be ethical in business.

My policies:

• Honest
• Professional
• No nonsense
• Friendly

My process:

• Getting requirements
• Concept design
• Price quote
• Design and implementation
• Testing
• After sales support

Some of the things we're proud of:

• We communicate in a language everyone understands.
• We keep tapped into the latest technical developments so our clients don't get left behind.
• We combine creative thinking with practical solutions.
• We are known for our attention to detail, but we see the big picture.
• We love what we do - and that can be contagious.

I bring consulting, technical and project management skills to the table; I don't expect the client to have any of those capabilities. So much the better if they do have them, but I don't expect it.

I hold the client responsible for being clear about the business outcome, and being committed to it.

I hold myself responsible for devising and producing a solution that is fit for purpose (with varying degrees of client and third-party assistance).

I expect the client to know:

• What they want as a business outcome. This would be some improvement in some area of their business operations.
• Why they want it. This is nearly always increased profitability, as a result of increased sales and/or reduced costs.

My job is to determine, sell and deliver:

• How to produce the solution. This is the solution design, development, validation, deployment, implementation and support.
• When the solution will be produced. This is the project schedule and milestones, including estimates and costs.
• Where the solution will be delivered. This is a statement of the solution's interfaces and integration with the client's business processes, infrastructure and application portfolio.

I believe there are two key requirements for a healthy consulting relationship:

• Honesty and integrity on both sides. Rule #1: I work with people I can trust (at least in terms of our shared business interests). I always give new clients the benefit of the doubt, but the first time the client shows me any kind of duplicity I go into damage control, followed by orderly disengagement.
• The client is committed to the business objective. As mentioned above, if the client knows what business result they want and why they want it and they are committed to it, then in general they will be involved, responsive and cooperative, they will listen to advice and recommendations, they will be reasonable and realistic, and they are willing to negotiate and pay a fair price to achieve the results they have committed to.

If the client can do that much, then that gives me confidence that I can do the rest.