Here it is: our own practical guide on how to get started on a collaboration with a software development company – and make the most of it!
If you’re well versed in such collaborations all this may come as no surprise. Rather, it would serve as a good checklist of meetings for you to compare with your own experiences. However, if you’re starting such an endeavour anew, you might find it to your purposeful liking.
When dealing with the progress of client company-software vendor relationship, two scenarios unfold. You, the client, according to your previous experiences, might find you’re in the position of either: A) a brand new client to a software vendor of choice, or B) an existing client of a software vendor, contemplating the possibility of a new project.
Regardless of where exactly you’re standing, one thing is certain: you got to the point of seeking out a software company because you’ve outlined a set of needs which will be expressed as business requirements. So yes, you’ve guessed it: every endeavour must start with you, the client, who needs to have an internal assessment of the opportunity of such a project.
Let’s take scenario A: new client company. Chances are you have already come into contact with a software provider at one point in your company’s history and so you know the course of action for the start of a collaboration. Just as well, you may have never worked with software providers before, so you’re about to find out what this course of action involves. No matter your degree of knowledge in this particular sense, you’re practically organising a selection process in which multiple companies engage contending for the role of your software product or services provider.
Now let’s assume you have a spot in scenario B: existing client company. Given that you’ve been working with a software company for some time now, your status spells familiarity with the course of action and your aim is to renew your existing partnership with a fresh project.
We’ve listed below the types of meetings a company will take part in after deciding to start a partnership with a software provider and how these meetings differ from one scenario to the other:
|New client company||Existing client company|
|Small series of workshops (optional)||Requirements clarification|
|Business proposal||Costs and timeline evaluation (via email)|
|Contract negotiation and sign-off||Go decision or Evaluation approval|
|Project initiation||Project initiation|
The selection process starts off with a sales meeting. For the best outcome, the people who should take part in this initial meeting on behalf of your company are: a procurement specialist, the business owner and possibly an IT specialist. Most likely, the people who’ll be joining you on behalf of your software-provider-to-be are a sales specialist and an account manager.
If everything goes well and you’ve made the choice that this company is the one for you, the next step to follow is the presales meeting. Expect to see a subject matter expert. Whereas the sales meeting does not require the presence of an IT specialist, the presales meeting cannot do without one.
Workshops are optional. They come in handy when your requirements are not very well defined yet.
Next up: the business proposal. This step is also carried out by the sales specialist. Ideally, your new software provider will present you will the timeline, budget and resources allocated to your project, and both of you will settle on a project methodology (e.g. Waterfall or Agile) in a discussion that will ensure you have a thorough understanding of how the project will be carried out and what internal resources you will need to mobilise – which will allow for smoother planning and elaboration of costs estimates.
Once the business proposal has been agreed upon, your procurement specialist negotiates the terms of the contract and the proposal itself. What follows is the contract sign-off.
The project initiation meeting that comes after signing the contract is mainly concerned with making sure everything is set and both parties are aligned for the start. The start of the project bears the name kick-off and follows through by means of the agreed methodology.
Eager for more details on the two scenarios? Episode two of our practical guide is on the way! If you’re too eager to wait, send us an email!