Website Development · Digital Products · Apps · AR · AI · Gaming · LMS

Website Development & Digital Product Strategy Built Around the Idea Before the Code

Websites, apps, portals, augmented-reality experiences, games, learning systems and AI products all eventually become software.

But the code is not the idea.

I help organizations figure out what should be built, who it is for, what should happen when people use it, what story the experience tells, how it creates value and which technology is actually appropriate. Then I can help shape the brief, guide the work and, when specialized engineering is required, connect clients with developers I trust.

The Short Version

I approach website development and digital-product development as a strategy problem before treating them as engineering problems. I help define the audience, idea, product story, user experience, business model, information flow, requirements and success criteria. Some projects I can help execute directly. Others belong with specialized software, app, game, immersive or learning-technology developers, and I can help select, brief, refer or coordinate those specialists without pretending every technology belongs under one roof.

The Code Is Not the Idea

The hardest question in software development is often not “Can we build it?”

It is:

Should we build it?

And if the answer is yes:

What exactly are we trying to make happen?

Modern development tools are astonishingly powerful.

Skilled developers can build databases, applications, APIs, 3D environments, recommendation systems, dashboards, learning platforms, games and immersive experiences that would have sounded absurdly ambitious not very long ago.

But excellent engineering can still produce the wrong product.

It can produce a beautiful app nobody has a reason to open.

A learning system nobody wants to learn in.

An augmented-reality experience that causes people to say “that's neat” for twelve seconds before never using it again.

Or a custom platform that recreates something an existing product already did perfectly well for a fraction of the cost.

A brilliant developer should not have to reverse-engineer your business strategy from a collection of feature requests.

Website Development Has Become a Very Large Category

Sometimes the “website” is actually software.

A traditional marketing website primarily publishes information.

A more sophisticated digital product may authenticate users, query databases, process transactions, personalize content, communicate with other systems, store user states, track progress, create recommendations or control real-world interactions.

At that point we are no longer just deciding what the About page should say.

We are designing behavior.

The project may involve:

  • Custom web applications
  • Mobile applications
  • Progressive web apps
  • Customer or member portals
  • Dashboards
  • Marketplaces
  • Ecommerce platforms
  • Learning management systems
  • Games and gamified experiences
  • Augmented reality
  • Virtual and spatial experiences
  • AI-powered applications
  • Conversational interfaces
  • Workflow systems
  • APIs and integrations
  • Data-driven interactive experiences

The moment a user can do something meaningful inside the experience, product strategy becomes at least as important as page design.

Digital Product Strategy

Before choosing the technology, I want to understand the experience.

Problem

What problem disappears?

If the product succeeds, what becomes easier, faster, more useful, more entertaining, more understandable or more valuable?

User

Who actually uses it?

The buyer and user may not even be the same person. Enterprise software, education and healthcare make that distinction particularly important.

Moment

When does it become useful?

At home? In a store? On a factory floor? In a museum? During training? While traveling? When something breaks?

Story

What journey are we creating?

Even utility products have narratives: before, action, feedback, progress and outcome.

Behavior

What should the user do?

Browse, learn, buy, create, solve, practice, explore, collaborate, upload, compare, communicate or return?

Value

Why come back?

Downloading an app is not loyalty. Long-term value comes from repeated usefulness, progress, identity, convenience, entertainment or belonging.

Economics

How does it support the business?

Direct sales, subscription, membership, retention, efficiency, lead generation, sponsorship, education, upsell or brand value?

Evidence

How will we know?

Define meaningful adoption and business outcomes before launch rather than celebrating whatever metric looks best afterward.

Technology

What is the simplest appropriate build?

Sometimes the right answer is a custom application. Sometimes it is WordPress, SaaS, a PWA, an API integration or something that already exists.

Build, Buy, Configure or Integrate?

Custom development should earn the right to exist.

Approach Usually Makes Sense When Main Risk
Configure an existing platform A mature product already solves most of the problem and differentiation does not depend on owning the code. Forcing the business into awkward platform limitations.
Integrate multiple systems The functionality already exists in different products but the customer or operational journey needs them connected. Creating brittle dependencies and confusing data ownership.
Build a custom web application The workflow, experience, business rules or customer value genuinely require software specific to the organization. Underestimating long-term maintenance and product ownership.
Build a mobile app Device capabilities, frequent use, offline behavior, location, camera, notifications or app-store distribution create meaningful value. Building an app merely because somebody said, “We should have an app.”
Build immersive / AR Spatial context actually improves visualization, learning, navigation, entertainment or task performance. Technology becoming the attraction instead of supporting the experience.
Build a game Agency, challenge, progression, competition, simulation or play is central to the experience. Calling points and badges a game without designing actual play.

I have no philosophical objection to custom software. I have a strong objection to spending custom-software money to solve a problem that did not require custom software.

Mobile App & Web App Strategy

An app needs a reason to occupy somebody's phone.

I like apps.

I also delete them.

So does everyone else.

The strategic question is not whether an app can be built.

It is whether the experience becomes meaningfully better because it is an app.

Device-native applications can make sense when the experience benefits from notifications, offline access, cameras, location, sensors, authentication, payments, saved state or repeated use.

But some ideas can be delivered beautifully as responsive web applications or Progressive Web Apps without asking customers to visit an app store first.

App strategy questions

  • Why would someone install it?
  • Why would they keep it?
  • What happens on first use?
  • What is the activation moment?
  • What requires an account?
  • What should work offline?
  • What data is collected?
  • Which device capabilities matter?
  • How does the business communicate without becoming annoying?
  • What should happen on the website instead?
  • What happens when the user changes devices?
  • How will support and updates work?

Native Apps

iOS and Android experiences when platform-specific capabilities or distribution justify native development.

Cross-Platform Apps

Shared-code approaches may reduce duplicated effort when product requirements and performance needs fit the model.

Progressive Web Apps

Web-delivered applications can provide installable and app-like experiences without automatically requiring native distribution.

Web Applications

Browser-based products can support dashboards, portals, software tools, workflows and interactive customer experiences.

Augmented Reality · Spatial Computing · Immersive Experience

AR is most interesting when it makes the real world more useful—not when it merely proves the camera works.

Augmented reality can put digital information into physical context.

That opens possibilities traditional pages cannot provide.

A customer can visualize a product in a room.

A museum visitor can see an interpretation layered onto a historic site.

A technician can receive guidance while looking at equipment.

A learner can interact with a three-dimensional object instead of merely reading about it.

A tourist can unlock location-dependent stories.

A retailer can let someone experience a product before ownership.

That is interesting because the technology changes the relationship between information and place.

AR can support:

  • Product visualization
  • Retail try-on or placement
  • Museums and historic interpretation
  • Tourism experiences
  • Industrial guidance
  • Field service
  • Training and simulation
  • Architecture and property visualization
  • Interactive exhibits
  • Branded entertainment
  • Location-based experiences
  • Education and science communication
The Experience Comes First

“Let's do AR” is not yet an idea.

What should the person see?

Why should seeing it spatially be better?

What should they understand afterward?

Does the experience need a native app?

Could it work through the web?

Does location matter?

Is this primarily education, entertainment, utility, commerce or storytelling?

Those questions determine whether AR becomes useful product design or a very expensive demo at a board meeting.

Gaming · Gamification · Interactive Storytelling

A game is not a website with points glued to it.

Games are interesting because they turn audiences into participants.

Instead of merely receiving information, the person makes choices.

Choices create consequences.

Consequences create feedback.

Feedback creates learning, challenge, mastery, discovery or entertainment.

That basic loop can be used far beyond conventional commercial games.

Interactive and game concepts can support:

  • Museum interpretation
  • Destination discovery
  • Brand engagement
  • Training
  • Education
  • Safety simulation
  • Employee onboarding
  • Customer loyalty
  • Trade-show experiences
  • Theme parks and attractions
  • Science communication
  • Community and social experiences
Agency

Choice

The participant needs meaningful decisions rather than merely clicking “next.”

Challenge

Difficulty

Too easy becomes boring. Too difficult becomes frustrating. The intended audience matters enormously.

Feedback

Response

Users need to understand what happened and how their actions affected the experience.

Progress

Momentum

Levels, skills, discovery, collection, achievement and narrative can give people a reason to continue.

Story

Meaning

Great mechanics can become much more memorable when the participant understands why the activity matters.

Social

Other People

Competition, cooperation, community and shared achievement can radically alter engagement.

Reward

Motivation

The reward should support the experience rather than replace intrinsic interest with meaningless badges.

Return

Replay

A strong experience gives people a reason to return that is deeper than receiving another push notification.

Gamification fails when somebody starts with points. Good interactive design starts with motivation.

LMS · E-Learning · Training Platforms

An LMS can track learning. That does not automatically mean learning is happening.

Learning Management Systems can organize courses, users, permissions, content, assessments, certifications, progress and reporting.

That infrastructure is valuable.

But the system should not be confused with the learning experience.

If every course is a forty-eight-slide presentation followed by ten multiple-choice questions, the platform may be functioning perfectly while everyone involved quietly loses the will to live.

The harder questions are instructional.

What should someone understand?

What should they be able to do?

How should information be sequenced?

Where should learners practice?

What feedback helps?

What genuinely demonstrates competency?

LMS and learning strategy can include:

  • Course architecture
  • Learning journeys
  • Instructional storytelling
  • Video and interactive content
  • Assessments
  • Certification
  • Progress tracking
  • Cohorts
  • Community
  • Onboarding
  • Compliance training
  • Continuing education
  • Customer education
  • Employee training
  • Partner or dealer education
Learning Technology Has an Ecosystem

The LMS may need to communicate with more than the learner.

Organizations may need identity management, course enrollment, content libraries, grading, external tools, reporting, HR systems, credentialing or ecommerce.

That is why interoperability becomes part of the architecture.

1EdTech's Learning Tools Interoperability standard, currently LTI 1.3, exists specifically to connect learning platforms with external learning tools and content in a standardized way.

Standards and integrations matter.

But the learner still does not care how elegant the integration is if the course is terrible.

AI Applications · Assistants · Agents · Intelligent Interfaces

Adding AI is easy. Giving it a useful job is harder.

Retrieval

Find the right knowledge.

AI applications can help people navigate large bodies of documentation, products, research, policies, content or institutional knowledge.

Assistance

Help someone complete a task.

Useful copilots reduce effort, explain complex information, create drafts or guide work while keeping appropriate human oversight.

Conversation

Replace menus with questions.

Conversational interfaces can let people describe what they need naturally rather than learning the organization's internal taxonomy first.

Personalization

Adapt the experience.

When appropriate and responsibly implemented, data can help tailor recommendations, learning paths, product choices and next steps.

Workflow

Connect intelligence to action.

AI becomes more useful when it participates in a well-defined process instead of generating another piece of text someone has to copy somewhere else.

Governance

Define the boundaries.

Data access, privacy, accuracy, human review, risk, logging and failure behavior belong in product strategy before launch.

The useful AI question is rarely “Where can we add AI?” It is “What decision, task or experience becomes meaningfully better if intelligence is available here?”

Portals, Dashboards, Marketplaces & Business Systems

Sometimes the most valuable software is not public-facing at all.

Customer Portals

Accounts, documents, status, messaging, orders, billing, support and self-service.

Member Portals

Content access, directories, events, education, benefits, community and membership management.

Dashboards

Turn operational or commercial data into information somebody can actually use to make a decision.

Marketplaces

Multi-party discovery, listings, transactions, trust, identity, payments and platform economics.

Workflow Applications

Replace manual handoffs, spreadsheets and email chains with structured processes where the economics justify it.

Internal Tools

Employees often deserve better digital experiences too, particularly when poor internal systems create customer-facing consequences.

Data Products

Search, analysis, visualization, reporting and decision tools can turn proprietary information into a usable asset.

Ecommerce Systems

Products, subscriptions, complex pricing, fulfillment, account relationships and integrations can move well beyond a simple storefront.

Story Is Not Just for Marketing

Every digital product tells the user what is happening, why it matters and what they should do next.

I use the word story broadly here.

A game has an obvious narrative.

A museum AR experience may literally tell history.

But a customer portal has a story too.

You arrived because something needed to happen.

The system recognized where you are.

It showed what matters.

You made a decision.

Something changed.

You received feedback.

You know what happens next.

Good experience design creates coherence.

The interface should tell the same story as the business logic.

The language should match the user.

The interaction should reflect the importance of the task.

The feedback should reduce uncertainty.

The technology should disappear enough that the person can concentrate on what they came to do.

That is why my background in writing, storytelling, strategy, science and customer behavior matters even when the ultimate deliverable contains a great deal of code.

See my background and credentials →

The best technology often feels less like technology and more like the obvious way the experience should have worked all along.

Technical Architecture Still Matters

Good product thinking eventually has to survive contact with engineering.

Front End

Interface, interaction, responsive behavior, accessibility and the experience users actually touch.

Back End

Business logic, authentication, permissions, data processing, workflows and server-side behavior.

APIs

Well-designed interfaces allow systems to exchange data and capabilities without rebuilding everything inside one application.

Databases

The data model matters because software can only reason cleanly about information that has been structured thoughtfully.

Identity & Permissions

Accounts, roles, authentication and authorization become essential when different users should see or do different things.

Cloud & Infrastructure

Hosting, deployment, scaling, logging, availability and operational requirements affect architecture long after launch.

Security

Threat model, data sensitivity, access, dependencies, updates and incident planning should reflect actual risk.

Privacy

Collecting information because software makes it possible is not the same thing as having a legitimate reason to collect it.

Analytics

Instrumentation should help explain adoption, friction, behavior and business outcomes without turning users into lab specimens.

User Need
Interface Interaction
Logic Rules
Data State
Systems Integration
Outcome Value
Accessibility, Security & Failure States

Product design includes what happens when things do not go perfectly.

Accessibility

Interfaces should consider keyboard use, focus states, semantics, contrast, touch targets, alternatives to visual information and the needs of people using assistive technologies.

Error States

“Something went wrong” is rarely enough. Good products help the person understand whether to retry, correct, wait, contact someone or do something else.

Empty States

What does the application show before data exists? The first experience should not look broken simply because the user is new.

Permission States

Applications should explain why they need camera, location, notifications or other access rather than behaving as though permission is owed.

Recovery

Password resets, interrupted transactions, lost connectivity and failed uploads are part of real product design, not edge cases we pretend nobody will encounter.

Human Support

Sometimes the correct digital experience is a graceful transition to an actual person.

I Am Not Going to Pretend I Personally Write Every Kind of Code

Some projects need specialists. I think that is a feature, not an embarrassment.

There are developers whose entire professional lives are mobile applications.

Others live inside Unity, Unreal, 3D pipelines, cloud architecture, security, enterprise systems, learning platforms or highly specialized front-end frameworks.

I do not believe the client benefits when one person pretends to be the world's best specialist in all of those things.

My highest-value role can be considerably earlier in the process:

Define the idea.

Understand the customer.

Pressure-test the business case.

Shape the story and experience.

Turn vague ambition into a useful product brief.

Determine what kind of development capability the work actually requires.

Then put the right people on it.

I would rather bring the right specialist into the room than pretend the right specialist was me all along.

Why This Model Works

Developers should be solving engineering problems—not trying to discover the company's entire strategy during sprint planning.

Better briefs

Clear objectives, audiences, journeys, requirements and priorities reduce ambiguity before technical work becomes expensive.

Better specialist fit

A serious game, an LMS integration and a complex B2B web platform may require very different technical teams.

Less feature inflation

Product strategy helps distinguish what the product genuinely needs from what merely sounded interesting in a meeting.

Customer continuity

The business, brand, user experience, marketing and eventual technology remain part of one idea rather than separate vendor conversations.

Commercial discipline

The project remains connected to adoption, revenue, retention, learning, efficiency or whatever outcome justified the investment.

Independent judgment

Because I am not required to sell a particular engineering stack, I can ask whether custom development is even the right answer.

How I Approach a Development Project

I would rather discover the expensive mistake on a whiteboard than after six months of development.

Business objective

Establish what the project is intended to change for the organization and why the investment deserves attention now.

User definition

Identify who uses the product, who buys it, who influences adoption and which problems matter to each audience.

Journey & story

Map what the person knows, does, sees, chooses and receives as they move through the experience.

Requirements

Translate desired behavior into functions, data needs, user roles, integrations and realistic constraints.

Build / buy analysis

Determine whether the best solution is custom engineering, platform configuration, integration or a hybrid approach.

Technical direction

Work with appropriate technical experts to select an architecture that fits scale, risk, platform and operational reality.

Prototype

Where appropriate, validate flows, content, interfaces or assumptions before committing to the full engineering effort.

Development

Build through the appropriate internal, partner or specialist development team using a clearer shared definition of the product.

QA

Test not only whether features technically function but whether humans can understand and successfully use them.

Launch

Deployment, migration, training, support, analytics and communication are part of getting the product into the world.

Observe

Watch adoption, completion, friction, errors, drop-off and qualitative feedback instead of assuming the roadmap was perfect.

Improve

A digital product is usually a living system. Prioritize the next release based on evidence and strategic value.

Measure the Product According to Its Job

Ten thousand users can be extraordinary or catastrophic depending on the business model.

Activation

Do users reach the moment where they first receive meaningful value?

Completion

Can people successfully finish the transaction, lesson, workflow or task?

Retention

Does the experience provide enough continuing value for appropriate users to return?

Revenue

Purchases, subscriptions, upsells, membership, pipeline or commercial value where the product is revenue-facing.

Efficiency

Time saved, errors reduced, support avoided or workflow improvements for operational systems.

Learning

Completion is useful, but demonstrated understanding, competency and behavior change may matter more.

Engagement

Meaningful interaction—not merely screen time engineered for its own sake.

Satisfaction

Qualitative feedback often explains why the analytics look the way they do.

Different Industries Create Different Products

Technology gets much more interesting when it solves an industry-specific problem.

Museums & Attractions

AR interpretation, visitor apps, games, memberships, digital exhibits, ticketing, location experiences and educational products.

Science & Deep Tech

Data tools, technical visualizations, simulations, customer portals, knowledge systems, training and product interfaces.

Manufacturing

Configure-to-order tools, customer portals, specification systems, field applications, training and workflow software.

Healthcare

Patient education, professional learning, portals and experience strategy where privacy, accessibility and risk require careful specialist involvement.

Associations

Member portals, learning, certification, directories, events, communities, content access and professional-development systems.

Nonprofits

Education, volunteer systems, member communities, donor experiences, program delivery and digital tools supporting mission.

Tourism & Destinations

Trip planning, AR, trails, digital passes, games, location-based storytelling and experiences connecting visitors with places.

Corporate Learning

Employee education, onboarding, certification, leadership training, partner learning and competency development.

Which Page Should You Be On?

Related digital problems require different kinds of work.

This Page

Website Development & Digital Products

Custom applications, portals, advanced integrations, apps, LMS, AR, gaming, AI products and experiences where software behavior is central.

Content-Led Business Site

WordPress Web Design

Best for business websites where strategy, content, SEO, GEO, voice, conversion and publishing architecture are primary.

WordPress Web Design →

Process

Marketing Automation & Workflow Design

Best when the core problem is routing, automation logic, CRM processes, lifecycle communication and connecting existing systems.

Automation & Workflow Design →

Leadership

Executive Strategy & Fractional CMO

Best when the larger problem is deciding how technology, marketing, product, vendors, customer acquisition and business priorities should work together.

Executive Strategy →

Scientist. Strategist. Storyteller. Technologist.

I am interested in the system underneath the screen.

My background in science makes me want to understand how the system actually behaves.

Strategy makes me ask why the organization should invest in it.

Marketing makes me ask who wants it and how the market will understand it.

Writing makes me ask what the person needs to understand next.

AI and machine-learning work make me think about data, intelligence, automation and how interfaces themselves are changing.

And years of digital work have taught me that the most expensive technical problems often started life as unclear business decisions.

Frequently Asked Questions

Website Development & Digital Product FAQs

What does a website development consultant do?
A website development consultant helps define what should be built, how the product should support users and the business, which requirements matter, what technology approach makes sense and how development should be organized. The role can include discovery, product strategy, information architecture, user journeys, requirements, vendor evaluation, development coordination, launch strategy and measurement.
Do you personally develop every application you advise on?
No. I handle strategy, product thinking and selected digital implementation directly, but advanced mobile applications, games, immersive experiences, enterprise software and other specialized builds may require developers whose expertise is concentrated in those technologies. In those cases I can help identify, refer, brief or coordinate appropriate development specialists rather than pretending every discipline belongs in-house.
Can you refer me to developers?
Yes. When a project requires specialized engineering, I can refer clients to or help coordinate developers and development companies I know and trust. I work with specialists based on the requirements of the project rather than forcing every project into one development model.
Can you stay involved after referring the development work?
Yes. Depending on the engagement, I can remain involved as a strategic advisor, help manage the brief, participate in product and vendor discussions, keep the customer experience aligned with the business objective and help connect development with marketing, content, launch and growth.
Do you consult on mobile app development?
Yes. I can advise on the underlying app concept, audience, user journey, feature priorities, product positioning, business model, requirements, launch strategy and whether a native application, cross-platform application, Progressive Web App or browser-based product is the most appropriate approach. Specialized engineering can be handled by the appropriate development partner when required.
Do you consult on augmented reality?
Yes. I advise on augmented-reality and immersive-experience concepts, especially where AR supports product visualization, tourism, museums, historic interpretation, training, science communication, field applications, retail or branded experiences. The first question is what spatial interaction improves for the user; the technical implementation can then be matched to platforms such as Apple AR technologies, Google ARCore, WebXR or specialized development environments.
Do you consult on games and gamification?
Yes. I can advise on game and gamification concepts where story, motivation, progression, feedback, challenge, agency, learning or audience engagement are important. The work may apply to attractions, museums, brands, training, education or other interactive experiences. Specialized game engineering and art production can be referred to appropriate developers when required.
Do you consult on LMS and online learning platforms?
Yes. I can help with learning-platform strategy, course architecture, learner journeys, instructional storytelling, engagement, assessment, certification, platform selection and how learning systems should connect with the broader organization. Specialized LMS implementation and standards-based integrations can involve appropriate learning-technology developers.
What is LTI?
Learning Tools Interoperability, or LTI, is a 1EdTech technical standard that allows learning-management systems and external learning tools or content to integrate in a standardized way. The current LTI 1.3 specification uses a more modern security model and supports services such as grade exchange, user-role information and deep linking.
Do you advise on AI applications?
Yes. I can help define useful AI application concepts, retrieval experiences, conversational interfaces, assistants, workflow integration, personalization, human-review requirements, product positioning and the business case behind adding AI. The goal is to give AI a useful job rather than adding it simply because the technology is available.
What is the difference between a custom website and a web application?
A conventional website primarily publishes and organizes information, although it may contain forms and other interactive features. A web application usually performs more substantial user-specific behavior such as authentication, data processing, saved states, dashboards, workflows, transactions, collaboration or custom business logic. Many modern projects contain characteristics of both.
Should my business build a custom application or use existing software?
That depends on whether custom software creates enough strategic or operational value to justify the cost and ongoing responsibility. If an existing product already solves the problem well, configuration or integration may be the better decision. Custom development makes more sense when important workflows, customer experiences, business rules or intellectual property genuinely require something specific.
Can you help write the product requirements or development brief?
Yes. One of the most valuable parts of my role can be translating business objectives, customer needs, user journeys and product ideas into a clearer brief before development begins. A better brief reduces ambiguity and gives developers a stronger basis for architecture, estimation and implementation.
Can you help evaluate development agencies or developers?
Yes. I can help leadership evaluate potential developers or development partners based on project fit, capabilities, communication, proposed architecture, understanding of the product, scope clarity and how well their approach aligns with the business objective. Highly specialized technical diligence may also require a specialist engineer or architect depending on the project.
How is this different from your WordPress web design service?
My WordPress web design service is primarily for content-led business websites where strategy, writing, information architecture, SEO, GEO, conversion and publishing are central. Website development extends further into custom application behavior, data, APIs, integrations, portals, apps, learning systems, games, AR, AI products and other software-driven experiences.
Do you help with launch and go-to-market strategy too?
Yes. A digital product is not finished merely because the code deploys successfully. Depending on the engagement, I can help with positioning, naming, audience strategy, messaging, pricing logic, onboarding, customer acquisition, SEO and AI discoverability, launch communications, sales enablement, analytics and the larger go-to-market system.
Do you work with companies outside Florida?
Yes. Paper Boat Media is based in DeLand, Florida, but I work with businesses, executives and organizations across the United States and selected international markets. Development teams and specialist partners can also be distributed according to the requirements of the project.
Paper Boat Media · Website Development & Digital Product Strategy

Bring me the idea before you bring somebody a specification.

Tell me what you think should exist.

Tell me who it is supposed to help.

Tell me why somebody would care.

Tell me what the business needs it to accomplish.

Maybe it becomes a website.

Maybe an app.

Maybe an augmented-reality experience, learning platform, game, customer portal, AI application or something neither of us has named correctly yet.

Maybe the smartest answer is not to build anything custom at all.

That is the conversation I want to have before somebody starts billing you to write the code.

Scroll to Top