Closed JMitnik closed 4 years ago
Slides Included are:
Note: Dashboard will not be shown as Mockup in order to not raise false expectations.
As opposed to the instantly integrateble webapp I will present us as consultancy and research organization. Before we can deliver any product we do an assessment of all useful touchpoints in the gym. Then we create the dialogues based on our expertise in the industry but also FROM INDIVIDUAL conversations with all managers and trainers (meaning coaches are supposed to tell us what kind of feedback they generally get so that we include this in the tree (will take alotta time). Finally our technical team must get familiar with their system so that eventual automations and API connections can be created.
Improve Dashboard and add Push-notification feature
Create Contract, keep in touch, add designs, arrange legalities and financial setup. Intensive Sales session to be invited by more gyms
We are now able to automate the creation of a personalized 6-Pager for any client in any industry. Personalisation means that by simply adding the Logo, Color Gradient and example Dialogue Endings it rethemes all pages of the Pitchdeck accordingly. This is a superpower for a salesman. While I have uploaded most pictures in Telegram already I will make this post here so that you know how we wanna communicate our value proposition. But I am now ready to paste single Assets into Figma.
PS. we now have 3 Demos :)
haas - Feedback 2.0 | by Markus Wogatzki | Anytime Fitness.pdf
For one of the early clients, we want to impress them by showing them a demo. After the last meeting, a list of requirements can be described as follows:
Important tasks
Client-side and API
Connect an API connection of all entries from the client-side
Setup the specific flow and leaf (custom user-input: email field and name)
Improve the slider (and grading) to be more smooth.
Reintroduce the moving-gradient from before
Add the SF-Pro fonts to the web
Nice-to-haves (only if the rest is finished)
Dashboard
Customer-overview basic CRUD operations: get a list of customers, be able to add customer, and also delete customer (top right). When a customer is added, also call a default seed to initialize a standard flow
[x] Read customers
[x] Create customer
[x] Seed customer
[ ] Update customer
[x] Delete customer
Topic-overview basic CRUD operations: get a list of topics, add a topic (for now, just default to the default flow
[x] Read topics
[ ] Create topic
[ ] Update topic
[ ] Delete topic
Aggregate of entries: have a basic aggregate overview of all entries
Timeline-view: history of question entries as they come in (refresh on reload for the moment)
Classic topic-builder: topic builder which can add, edit, connect, etc