Attributes or Things

gglass · 2025-01-20T22:19:17.152Z

I am building a simple app designed to help my tech sales new hires prospect and conduct cold calls effectively. Without any prior experience, I need them to select basic options, and the output needs to be content relevant to the options chosen.

Choose Department: (Infrastructure, Cloud, Networking, Applications, Operations, etc)
Choose Role: (Admin, Manager, Director, VP, CTO/CISO/CIO)
Known problems (Scalability, Operations, Cost Reduction, Security, etc)

Output =
{infrastructure} {manager} has a primary responsibility to oversee {role/job description here}. This job function typically reports to {boss role here} and has a typical budget authority of up to {$budget known here}.

When focused on {option 3 Known Issues here} Here are the top sales questions to ask that will help you qualify an opportunity:
{list 0-10 questions assigned exclusively to this role}

Here are additional resources and docs to share:
{list of white papers / case studies // internal docs}

My Question:
What is the easiest way to structure this data? Should this be 500 different “Things” or is there an easy Thing → Data Type → App Data → Option Sets that will produce the dynamic results needed?

Anything would help me get through this paralysis - thank you!
G.

LittleBubbler · 2025-01-21T00:30:19.194Z

Option sets seem to fit what you need.

Bear in mind that using option sets mean that you have the sets of answers needed & that they won’t change (unless you edit their entries). You don’t have to create them if the answer is static, reusable & you’d like to call them dynamically (meaning, in different places). You should be good.

mitchbaylis · 2025-01-22T05:24:37.143Z

if you want users to be able to edit the options in the app = data
if you want the options to be static and only edited in bubble dev = option set