24 Carrots Revised

Get Started. It's Free
or sign up with your email address
Rocket clouds
24 Carrots Revised by Mind Map: 24 Carrots Revised

1. Functional Entities

1.1. Event Builder

1.1.1. Proposals

1.1.1.1. can compare proposals

1.1.1.1.1. 25h

1.1.1.2. can send link to client of proposal

1.1.1.2.1. can comment on this link

1.1.1.2.2. client can sign proposal

1.1.1.2.3. mobile friendly

1.1.1.2.4. 50h

1.1.1.3. see(build) Proposal doc

1.1.1.3.1. will lay out all event details

1.1.1.3.2. 80h

1.1.2. Event Details

1.1.2.1. Menu

1.1.2.1.1. Add packages to menu

1.1.2.1.2. Estimated Menu Price and Cost factored into event estimates

1.1.2.1.3. 80h

1.1.2.2. Equipment

1.1.2.2.1. Should be linked to menu recipe items that require equipment

1.1.2.2.2. add equipment to event

1.1.2.2.3. 30h

1.1.2.3. Staffing

1.1.2.3.1. add roles to event

1.1.2.3.2. invite staff members to event

1.1.2.4. Venue

1.1.2.4.1. selected venue information

1.1.2.4.2. venue selection

1.1.2.4.3. 10h

1.1.2.5. Delivery Info

1.1.2.5.1. Food and Equipment Delivery

1.1.2.5.2. 30h

1.1.2.5.3. There can also be a set crew delivery (same fields)

1.1.2.6. Timeline

1.1.2.6.1. Associated time w/ description and internal note

1.1.2.6.2. 20h

1.1.2.7. Decor and Entertainment

1.1.2.7.1. Third Party Vendors

1.1.2.7.2. 25h

1.1.2.8. Fees

1.1.2.8.1. add from master list of fees

1.1.2.8.2. can edit the fee amount for the event

1.1.2.8.3. Fee can be flat-fee or on per person basis or percentage or percentage of segment

1.1.2.8.4. Including discounts

1.1.2.8.5. 40h

1.1.2.9. Event Based Reports

1.1.2.9.1. 40h

1.1.2.9.2. Kitchen BEO (Banquet Event Order)

1.1.2.9.3. Recipe Prep Sheet

1.1.2.9.4. Social Warehouse Packing List

1.1.2.9.5. Social BEO “Party Pack for Leads”

1.1.2.10. Info

1.1.2.10.1. Event Type

1.1.2.10.2. Status

1.1.2.10.3. Number of Guests

1.1.2.10.4. Salesperson

1.1.2.10.5. client

1.1.2.10.6. 40h

1.1.2.11. Estimated Cost and Price

1.1.2.11.1. Estimated profit

1.1.2.11.2. Show changes in price and cost

1.1.2.11.3. 10h

1.1.2.12. Event Change History

1.1.2.12.1. track of changes made to the event

1.1.2.12.2. 10h

1.1.2.13. Event Financial View

1.1.2.13.1. shows breakdown of balance due and breakdown of price by rev code

1.1.2.13.2. 20h

1.1.2.14. ability to attach docs: signed contracts

1.1.3. Calendar View

1.1.3.1. Calendar of all events with the number of events and their status

1.1.3.2. Sort/filter by Salesperson

1.1.3.3. search by event id

1.1.3.4. 20h

1.2. Reports

1.2.1. Purchase Order Guide

1.2.1.1. created from what ingredients and other items events need

1.2.1.1.1. cross checked against ingredient inventory

1.2.1.2. Over a date range

1.2.1.3. Uses Ingredients Purchase Units

1.2.2. Accounting Reports

1.2.2.1. Accounts Receivable

1.2.2.1.1. sort by salesperson or customer

1.2.2.1.2. Shows every event that has a balance

1.2.2.1.3. End date filter

1.2.2.2. Payments Received

1.2.2.2.1. matched up each day against daily credit card batches or bank deposits

1.2.2.2.2. Filter by payment type

1.2.2.2.3. Start and End Date filter

1.2.2.3. Revenue by Category

1.2.2.3.1. gross up all revenue codes income to apply income to QB

1.2.2.3.2. Start and End date filter

1.2.2.4. Rev by Code

1.2.2.4.1. similar to rev by category

1.2.2.4.2. start and end date filter

1.2.2.5. Sales Tax by Jurisdiction

1.2.2.5.1. Used to calculate and pay sales tax for company

1.2.2.5.2. shows breakdown of taxable and non taxable by event and sums them per jurisdiction

1.2.2.5.3. start and end date filter

1.2.3. export to excel or as pdf

1.2.4. Custom Report Builder

1.2.4.1. think Google Warehouse

1.2.4.2. similar to what we did for MKT CHP

1.2.5. 200h

1.3. Clients

1.3.1. Title, email, salesperson, address, contact, and contact type and number

1.3.1.1. Each contact should have an associated name and phone number

1.3.2. Need rich text editor Note for clients

1.3.3. Client's will generally have multiple addresses so we need to be able to handle that

1.3.3.1. could be similar to contact phone type

1.3.3.1.1. billing, mailing, office, alternate etc. types of addresses

1.3.4. need client type

1.3.4.1. corporate or social

1.3.5. 40h

1.3.6. need to track company name

1.3.7. search by address or phone number

1.3.8. need ability to have multiple emails similar to phone number

1.4. Accounting

1.4.1. Invoices

1.4.1.1. List of all invoices

1.4.1.2. Filter by date, time overdue, payment status, salesperson

1.4.1.3. Data

1.4.1.3.1. Event

1.4.1.3.2. Amount Due

1.4.1.3.3. Sales Person

1.4.1.3.4. Company

1.4.1.3.5. date created and due date

1.4.1.3.6. Time overrdue

1.4.1.3.7. Status

1.4.1.4. Ability to pay invoice or view invoice as PDF

1.4.1.4.1. they should be able to export any invoice as a PDF

1.4.1.4.2. Should be able to log a payment against an invoice to change the balance due

1.4.1.5. 80h

1.4.2. Payments

1.4.2.1. list of all payments

1.4.2.2. can add payment

1.4.2.2.1. payment type and amount

1.4.2.3. 40h

1.4.3. Sales Tax

1.4.3.1. list of area codes and their tax %

1.4.3.2. ability to input a future tax % and effective date

1.4.3.2.1. would affect all events after that date

1.4.3.3. 30h

1.4.4. Fees & discounts

1.4.4.1. fees can be on per guest or flat fee basis or percentage or percentage of segment (equipment)

1.4.4.1.1. Needs to be able to handle discounts as well

1.4.4.1.2. 100h

1.4.4.2. which company fee associated with

1.4.4.3. fee should have a price

1.4.4.3.1. price can be edited on event by event basis

1.4.4.4. Each needs to be associated with a revenue code so they can see where discounts were applied on the revenue

1.4.4.5. 20h

1.5. System Master List

1.5.1. packages

1.5.1.1. name, image, type, description, number serves, price, tags, note, alternate name

1.5.1.2. Calendar of when available

1.5.1.3. possible allergies

1.5.1.3.1. comes from underlying ingredients

1.5.1.4. add recipes to package

1.5.1.4.1. possible substitutes built into underlying recipe

1.5.1.4.2. underlying recipe ingredients drive package cost

1.5.1.5. 80h

1.5.2. recipes

1.5.2.1. name, image, type, category, description, number serves, price, tags, note, alternate name, Sub-Recipe, parent recipes

1.5.2.2. possible allergies

1.5.2.2.1. comes from underlying ingredients

1.5.2.3. add ingredients to recipe

1.5.2.3.1. preparation process

1.5.2.3.2. quantity used and usage measurement

1.5.2.3.3. special note

1.5.2.3.4. drives recipe cost

1.5.2.4. Recipe Prep instructions

1.5.2.4.1. text editor

1.5.2.5. equipment necessary for recipe

1.5.2.6. substitute recipes

1.5.2.6.1. built in by admin

1.5.2.6.2. associated up-charge (set by admin)

1.5.2.7. Calendar of when available

1.5.2.8. 80h

1.5.2.9. when recipe was sold for past events and for future events

1.5.3. ingredients

1.5.3.1. name, image, type, category, description, unit cost, tags, note

1.5.3.2. allergies

1.5.3.3. measurements

1.5.3.3.1. unit, purchase and usage measurements

1.5.3.3.2. linked to master list of measurements

1.5.3.4. substitute ingredients

1.5.3.5. Loss Percentage

1.5.3.5.1. given when entered

1.5.3.5.2. the weight or amount of the ingredient that is used up in preparation of that ingredient

1.5.3.6. Calendar of when available

1.5.3.7. 40h

1.5.3.8. when ingredient was sold for past events and for future events

1.5.4. venues

1.5.4.1. Name, Images, Description, Address, Contact Person, Contact # and email, Capacity, isOwned?

1.5.4.2. Flat Fee for venue; not per person or per hour

1.5.4.3. venue should have calendar associated with it showing availability

1.5.4.4. 25h

1.5.4.5. ability to attach docs: venue terms and contracts

1.5.5. Recipe Categories

1.5.5.1. name, description

1.5.5.2. recipes assigned from master recipe screen

1.5.5.3. H'orderves rebalancing within packages

1.5.5.4. important as a lot of time they sell their packages as "2 H'orderves, 2 Entrees and 2 Accompaniments"

1.5.5.5. 10h

1.5.6. Equipment

1.5.6.1. Name, description, price, quantity, turn around time, type, status, note, image

1.5.6.1.1. location: rack, row, location.

1.5.6.1.2. Equipment Owner

1.5.6.2. quantity available

1.5.6.2.1. determined in conjunction with total quantity, scheduled events usage of equipment, and turn around time

1.5.6.3. 20h

1.5.7. Allergies

1.5.7.1. Name, note and Description

1.5.7.2. tied to ingredients from ingredient master

1.5.7.3. 10h

1.5.8. Measurements

1.5.8.1. Label, Key, Custom

1.5.8.2. can be selected from ingredient master for unit, purchase and usage methods

1.5.8.2.1. custom measurements will require a given conversion

1.5.8.3. 10h

1.5.9. Vendors

1.5.9.1. Name, category, info, email, phone, address

1.5.9.2. 10h

1.5.10. Vendor category

1.5.10.1. 10h

1.5.11. Equipment category

1.5.11.1. 10h

1.5.12. bulk editing

1.5.12.1. only certain fields where applicable (mostly attach tags / change active date range etc)

1.5.12.2. 30h

1.6. Approvals

1.6.1. Chef approvals of custom menu items

1.6.2. Manager's approval if profit drops below threshold

1.6.3. 80h

1.7. Ingredient Inventory

1.7.1. both add and remove

1.7.1.1. reason for removal

1.7.2. 100h

1.8. Dashboard

1.8.1. Salesperson

1.8.1.1. current commission

1.8.1.2. Rev required to next commission and total rev

1.8.1.3. Payments Due for their events

1.8.1.4. Total Events and Events in next two weeks

1.8.1.5. 40h

1.8.2. Chef

1.8.2.1. see approvals needed

1.8.2.2. see events you are staffed to

1.8.2.3. 20h

1.9. Super admin

1.9.1. manage users

1.9.1.1. 25h

1.10. Drag and Drop Sorting

1.10.1. within event builder, recipe builder, and package builder

1.10.2. drag and drop order of packages, recipes, equipment etc.

1.10.3. 10h

2. Key

2.1. MVP

2.2. Likely Future Version

2.3. Need Clarity

2.4. Newly Added after Last Walkthrough

2.5. Complexity

2.5.1. Low

2.5.2. Medium

2.5.3. High

3. Other Project Info

3.1. Each order is given in two separate proposals/contracts from two separate 24 Carrots companies. This is so that one contract can remain tax-free to the customer. The system must support two different contracts with different products on each contract attributed to two different companies

3.2. Integration Points

3.2.1. Paycom

3.2.1.1. Time reports export

3.2.1.2. where they do payroll for employees

3.2.2. Delivery Routing Software

3.2.2.1. they are trying out a new software now

3.2.3. StaffMate

3.2.3.1. we will eventually replace in future version and do not necessarily need to integrate with but would help client if we could

3.2.3.2. where broadcast staff openings for their part-time employees to sign up for an event

3.3. Social Events and anything corporate over $5,000 needs to be paid upfront (usually whole amount but sometimes minimum $5,000; 10 days before generally). This would tie into the Payments due dashboard.

3.4. Revenue Codes

3.4.1. Important for when they import Rev into QB

3.4.2. All revenue from events need to be tied to the specific revenue code for that business segment whether that be Equipment, Food, Bev etc.

3.5. Exporting

3.5.1. throughout the application, they will need the ability to export as pdf or to excel

3.5.2. on any list

4. Technical

4.1. Modules

4.1.1. styled pdf generator

4.1.1.1. 40h

4.1.1.2. including prefix html template

4.1.2. online template editor

4.1.2.1. 60h

4.1.3. e-sign service integration

4.1.3.1. hello sign

4.1.3.1.1. 25h

4.1.4. email notification

4.1.4.1. 20h

4.2. Infrastructure

4.2.1. backend project setup

4.2.2. server setup

4.2.3. web project setup

4.2.4. 40h

4.3. Roles & Permissions

4.3.1. 40h

4.4. Email Auth Setup

4.4.1. 10h