Notes

Joint projects

A client wants a system. Where will your profit come from?

A client trusts you and asks: “Could you also build us a system?” You do not want to turn down revenue. Developers can be found. But before promising a price and a deadline, work out what you are selling and which work will stay with you.

An introduction or a full project

If you simply introduce the client to an IT team, they then agree on the job and delivery themselves. Any introduction fee needs discussing in advance. A recommendation does not create one automatically.

If you sell the project in your own name, the client will bring the problem to you, even when the developer made the mistake. You will have to clarify requirements, follow up on agreements and explain why something fails. That is work, and it belongs in the price.

There is also a joint arrangement. For example, you understand the client's sales process, prepare data and help staff move to the system. The technical partner builds the agreed part. Then it is clear what each person brings and which result they own.

The gap between two prices still has costs inside it

A hypothetical example: the client pays 10 units and development costs 7. Your process and data work costs 1.5, and you reserve another 0.5 for extra work. That leaves one unit before taxes and overheads. The owner's time must be paid for in this calculation too.

If development costs 8 instead of 7, the remainder disappears. Before promising a price, find out who pays for changes, what counts as additional work and when the project scope is reconsidered.

Calculate cash timing separately. Of those 10 units, the client initially pays 3. The developer needs a 3.5 advance, and your preparation takes another 1.5. You are two units short until the next payment. A deal can be profitable while you still lack the cash to deliver it.

What will you hand over to the client?

“Build a CRM” is too broad a promise. Suppose the client assembles proposals manually from several spreadsheets. You could choose five different real orders beforehand and check that the salesperson can produce a proposal with current prices and stock, while the manager can see its status.

Then you need ordinary answers: who provides data, who makes decisions for the client, how the result is checked, when payments happen and what to do when the task changes. If the client has nobody with time for that work, hiring a good programmer will not fix it.

Your own IT team after one order is an expensive idea

You can do one project with a technical partner. Afterwards, you will see how much work there really was, what you earned and whether there are more customers. Permanent staff need a steady workload. Hiring people is usually easier than finding profitable work for them every month.

My part is business development, key relationships and choosing new directions. The Sailet team handles development and project delivery. If you have a client job and understand your contribution, we can discuss a joint project. Commercial terms depend on that job and the parties' agreements.

Do you have a client project?

Describe what the client wants to change, which work you will do and where you need a technical team. We can start with the job and the numbers.

Write about the project

Reasons to get in touch

Already have a defined implementation project? Talk to the Sailet team