Sales Qualification WebApp - Stuck on how to best structure the database and results view

[gglass]

Afternoon all,
New to Bubble and a big fan already. I have what feels like a silly question, but I could use your help.

The expected user/audience of this app is a small (under 30) sales and market (or lead dev) development reps at a global IT company (IBM). We have an enormous amount of onboarding training tools, customer case studies, white papers, industry events, thousands of product SKUs, and many other tools like SFDC for sales opty management / quoting / forecasting, etc. But all of these resources are very spread out across a ton of internal sites. Senior sellers have little trouble with this. but new hires (new to technology sales jobs) are stuck.

In light of all of these sales enablement tools and internal resources, the biggest problem is skills development. Most new hires are very intelligent and very capable young professional sales people. But they have no idea how to prospect, cold call, or navigate simple project qualification meetings with our IT buyers.

Challenge:
"as a new hire, I have access to a ton of great tools, resources and training guides to better understand our product(s) features and functions, solution capabilities and customer value prop. I also have a ton of leads to cold call and qualify. But I have no idea who our buyer is, what they do/dont do, or what questions to ask during our call to qualify them.

Solution:
A simple webapp that allows the user to Login > select an IT buyer persona (dropdown) > Select the primary IT driver or objective > and within a few clicks - see a curated list of results with “Top 20” sales questions to ask the IT buyer being cold called. No tech or sales experience needed.

My idiots guide to the logic of this webapp:
User login > lands on Account Dashboard (image attached) > Launch Webapp

Select IT Dept> (ex: Infrastructure, Applications, Cloud, Security, Networking, etc)
Select IT Role (ex: Engineer, Admin, Manager, Director, VP, CTO/CISO/CXO)
Choose Primary Driver (ex: Reduce IT operational costs, Optimize IT resources, Increase CyberSecurity Posture, Automate management processes, etc)

Example Output (see doc attached for reference):
Dept // Role // Job Function & Responsibilities // Top Recommended Sales Questions // Related Product Recommendations

ex:
Persona Selected = Infrastructure Manager
Persona Role Details = The infrastructure manager is typically responsible for . This role is directly accountable for <xyz job functions // IT business outcomes> and indirectly responsible for . They typically report to the IT Director or CTO and can approve IT purchases up to $10,000 w/o Exec Approval.
Top 20 Recommended Qualification Questions = <list of questions relevant to the dept/role/IT driver options selected>
Recommended Product(s) = <list relevant product features/functions to recommend - related to the dept/role/IT driver options selected>

==

My Ask:
What is the best way to structure this data and simplify the results details?
Should this be built using Multiple database Things with various input fields, App Data and Option Sets? Is this better built as a series of products that gives my users an ecommerce shop experience – with results in List view and Product Detail view, using product attributes or option sets as webapp structure?

I want my users to login > select a persona > Understand what they do / dont do, ask them thoughtful questions that are directly relevant to their role/responsibilities, and share topic-relevant content like KB Links, Customer Case Studies, Whitepapers, upcoming events and other content aggregated in the webapp results page.

I really appreciate your feedback and help here, Thank you!

[Bubbleboy]

Various way to approach this but a simple approach might be:

1. Persona thing, this is where you can specify the buying persona e.g IT Manager, IT Director, CTO, CRO, Head of HR, the list goes on and on. You could add attributes for each if the given persona is a decision maker or decision influencer etc . if your target audience follow a given sales methodology such as M.E.D.D.I.C your Personas can match the guiding principle of that sales methodology for consistency.

The persona thing could then a have a list of ‘Discovery question things’ These would be obviously all the various discovery questions that help guide encourage the seller to glean the pains, gains and stay awake issues of the persona in question. Basically, help them qualify.

The Persona thing could then also have a list of ‘Collateral things’ Case studies, testimonials, white papers etc that would be available when the persona is selected, adding an additional veneer of insight which might help the seller position they discovery probing.

The UI could follow the general approach of a form builder type interface where the author /creator could add/update reorder discovery questions and add edit additional collateral.

There is a very obvious case for add or applying AI here

[gglass]

Hey BubbleBoy
Thank you for your reply here, youre right on. A step deeper into structure, would you be building 3 “things” here (Persona, Discovery Questions and Collateral)? If so, how would you structure “Persona”
Role = text field (or dropdown) (admin, manager, director, vp, etc)
Dept = text field (or dropdown) (cloud, security, infrastructure, etc)
Decision Maker/Influencer = toggle? (keep it simple w/ checkbox?)
Collateral = {needs to support text, links, doc upload and download}
…limited Bubble understanding here, but should I make this collateral section a {hidden blog post} - that holds text, links, images, docs, etc - and then assign it here in the Persona Thing as an attribute SRC somehow?

Last - multi-step or muliti-page click path for users - or publish on single page with dropdowns on single row at top? What is the easiest ways to make multiple dropdown options dependent on each other? And then load results on same page?
ex:
dropdown 1 = Network Operations | dropdown 2 = Manager | dd 3 = Issues/Problems

output = dynamic content based on user selections + collateral thing + recommended products

Thank you!
G.

[gglass]

portions of this may apply. thoughts?

Learn to Build an AI app with Bubble

[Bubbleboy]

By your own volition “you’ve limited Bubble understanding”. That’s not a bad thing but don’t run before you can walk. (humble suggestion from my own experience).
The points and questions you’ve raised are all logical and valid but i would suggest you need to step back and focus on the use case/s
for example:

1. Is this app simply a reference for sellers or are you intending for the seller to interact (like a guiding selling tool)
2. Do you intend (if it’s the latter) to display different content/qualification guidelines based on information gleaned from the prospect by the seller. e.g do you have budget yes displays different content to no. Is there a compelling event etc
3. Capturing information from the seller e.g what’s the risk of doing nothing
   Once you’ve got a clear view of the use cases, then I would highly recommend you do the courses. This will provide you with the fundamentals to make informed decisions on all the points you’ve raised.
   What I can say with certainty is the high level aspirations you have in mind for your app is ideally suited to be built in bubble by you.