Business plan in Lucidchart

Tekentool 

Productnaam: Lucidchart.com
Naam van de fabrikant: Lucid Software Inc.

Voor dit business plan, maakten we gebruik van de tekentool genaamd 'Lucidchart'. Hiermee hebben we een bedrijfsproces uitgetekend. Dit biedt de mogelijkheid om een bedrijfsproces voor iedereen in de onderneming duidelijk weer te geven. Voor zoiets uit te tekenen, moet je goed weten welke vormen/ figuren je moet gaan gebruiken. Als je dit eenmaal weet en het programma goed onder de knie hebt, is het zeer eenvoudig te gebruiken.  Wij hebben gebruik gemaakt van de gratis versie waardoor we het business plan moesten opsplitsen in 2 delen. Voor de rest, hebben wij eigenlijk geen problemen ondervonden met de gratis versie.

Zakelijk proces

1. We are provided with a customer lead

2. A sales qualification process starts, according to the BANT methodology.
(BANT=Budget, Authority, Need and Timing)

The first 3 checkpoints of the BANT methodology (Budget, Authority, Need) are performed in parallel in order to speed up things:

BANT checkpoint Who? (Performs the check) What? (Action)
Budget Sales Rep.

• Check if the customer has budget set aside for this purchase? What is it?

Authority Sales Rep.

• Whose budget will the purchase come out of?
• Who else will be involved in the purchasing decision?

Need Solution architect

• What challenge does this purchase solve?
• Why do you feel it's worth solving?
• Why hasn't it been addressed before?
• Does the customer need match what we as a supplier can deliver?

Timeline Resource planner

• When do you need a solution in place by?
• Do we have the resources and is it feasable to deliver within the timeframe the customer wants?

3. The qualification meeting is split up in 2 phases: First the B-A-N findings are discussed (Sales Manager, Sales Rep, Solution Architect present). If this conclusion is negative, the qualification meeting ends. Else, it continues with calling in the Resource Planner to the meeting, who provides input on the resource planning feasibility (T-element of BANT, do we have the people and means). The final decision in this qualification meeting is made by the Sales Manager, hosting this meeting, based upon the input provided by the contributors to the BANT process.

The outcome of the qualification meeting is communicated to the customer: If after the meeting, the advice is to continue, the sales rep. informs the customer of our intention to work on this request. If the advice is not to continue, the sales informs the customer of the fact he will not get a reply from us.

4. Now the following teams will start working at the same time:

• The solution architect will work out the project solution.
• A calculator works out the project cost
• Our accounting department performs a credit check on the customer, to validate its financial health.

5. When done, a management meeting is held which gives the final go/no-go and approves the profit margin to use. If no-go, the customer is informed by the sales rep. he will not receive a proposal. If go, the final proposal is prepared by the solution architect, and handed to the customer by the sales rep.

1. We are provided with a customer lead

2. A sales qualification process starts, according to the BANT methodology.
(BANT=Budget, Authority, Need and Timing)

The first 3 checkpoints of the BANT methodology (Budget, Authority, Need) are performed in parallel in order to speed up things:

BANT checkpoint Who? (Performs the check) What? (Action)
Budget Sales Rep.

• Check if the customer has budget set aside for this purchase? What is it?

Authority Sales Rep.

• Whose budget will the purchase come out of?
• Who else will be involved in the purchasing decision?

Need Solution architect

• What challenge does this purchase solve?
• Why do you feel it's worth solving?
• Why hasn't it been addressed before?
• Does the customer need match what we as a supplier can deliver?

Timeline Resource planner

• When do you need a solution in place by?
• Do we have the resources and is it feasable to deliver within the timeframe the customer wants?

3. The qualification meeting is split up in 2 phases: First the B-A-N findings are discussed (Sales Manager, Sales Rep, Solution Architect present). If this conclusion is negative, the qualification meeting ends. Else, it continues with calling in the Resource Planner to the meeting, who provides input on the resource planning feasibility (T-element of BANT, do we have the people and means). The final decision in this qualification meeting is made by the Sales Manager, hosting this meeting, based upon the input provided by the contributors to the BANT process.

The outcome of the qualification meeting is communicated to the customer: If after the meeting, the advice is to continue, the sales rep. informs the customer of our intention to work on this request. If the advice is not to continue, the sales informs the customer of the fact he will not get a reply from us.

4. Now the following teams will start working at the same time:

• The solution architect will work out the project solution.
• A calculator works out the project cost
• Our accounting department performs a credit check on the customer, to validate its financial health.

5. When done, a management meeting is held which gives the final go/no-go and approves the profit margin to use. If no-go, the customer is informed by the sales rep. he will not receive a proposal. If go, the final proposal is prepared by the solution architect, and handed to the customer by the sales rep.

UML Activity Diagram