- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- Data Management Policy
- strategy
- values
- Operations
- Product
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Customer Stories
- Social Media
- blog
- Community
- Marketing - Website
- FlowFuse Messaging
- Webinars
- Sales
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- Production Environment
- FlowFuse Dedicated
- Staging Environment
- Project Management
- Releases
- Security Policy
- tools
- Website A/B Testing
- Internal Operations
- People Ops
To understand the prospective customers needs and how FlowFuse can help a process has been created to enhance their experience. Almost all engagements with customers are on virtual sites, generally Google Meet.
# Meeting a customer
For internal training purposes all sales calls should be recorded after getting explicit consent from the customer. On request of the customer, the recording will be shared.
The organizer of the meeting should perform pre-call preparation, including research on the prospective customer, any goals they have shared, any goals we have, and any relevant background information so all FlowFuse participants can know what to expect.
For each meeting, be 2 minutes early. This allows everyone to check their setup and sync up what the goals are for the meeting.
# Meeting structure
The number of times FlowFuse will meet with a customer depends mostly on the customer. However, in all cases FlowFuse would like to have an initial Discovery Call.
A discovery call is generally followed by a Demo.
To validate the solution to the problem the customer is experiencing, FlowFuse will aid in a POC.