Skip to main content

Product Context

Understanding NetPad's Users and Marketโ€‹


Why NetPad Existsโ€‹

Internal tooling at SMBs is broken. Teams need tools for data collection, routing, and workflow automation, but their options are:

OptionReality
Enterprise SaaS$50+/user/month, overkill features, vendor lock-in
Custom Development3+ months of dev time they don't have
No-Code CombosTypeform + Zapier + Airtable = integration nightmares

NetPad's insight: Most internal tools follow the same patternโ€”collect data, store it, route it, act on it. We make that loop fast with native MongoDB integration.


Target Usersโ€‹

Primary: Internal Platform Teams at SMBsโ€‹

Profile:

  • Company size: 50-500 employees (sweet spot)
  • Role: IT managers, operations leads, platform teams
  • Technical level: Can follow instructions, not full developers

Priority Verticals:

VerticalWhyExample Use Cases
FinanceCompliance needs, approval workflowsExpense reports, budget requests, audit trails
HealthcareData collection requirements, HIPAA concernsPatient intake, medical history, appointment scheduling

Pain Points:

  • "We need this tool yesterday but dev team is busy for 3 months"
  • "Our current solution costs $X per seat and we only use 10% of it"
  • "Data lives in 5 different tools that don't talk to each other"

What They Evaluate:

  • Time to first working app (target: under 30 minutes)
  • Can it connect to our existing MongoDB?
  • Does it handle our workflow/routing needs?
  • What does deployment look like?
  • What's the escape hatch if we outgrow it?

Secondary: Developers Evaluating Build vs. Buyโ€‹

Profile:

  • Senior developers or tech leads
  • Researching internal tooling options
  • Will inspect code quality and architecture first

What They Care About:

  • Is the architecture sound?
  • Can I extend it if needed?
  • Is there lock-in? (Open source + export = no lock-in)
  • How does it compare to Retool/Appsmith?

Where They Find Us:

  • GitHub (inspect the repo)
  • Hacker News discussions
  • Technical blog posts
  • Word of mouth from other developers

User Journeysโ€‹

Journey 1: IT Manager Needs a Help Deskโ€‹

Scenario: Sarah manages IT at a 200-person company. Employees email her directly with issues, things get lost, there's no tracking.

Current Pain:

  • Issues come via email, Slack, hallway conversations
  • No way to prioritize or track resolution
  • Can't report on response times to leadership

NetPad Journey:

  1. Finds NetPad via search for "internal help desk without Zendesk"
  2. Signs up, sees IT Help Desk template
  3. Customizes fields for her environment (adds department dropdown)
  4. Creates workflow: route high-priority to Slack #it-urgent
  5. Deploys form to company intranet
  6. Tracks submissions in Data Browser

Success Metric: Working help desk in 30 minutes, not 3 months.


Journey 2: Developer Evaluating Optionsโ€‹

Scenario: Marcus is a senior dev at a fintech. Product wants internal tools but his team is fully allocated to the main product.

Current Pain:

  • Backlog of internal tool requests
  • Previous "quick" internal projects became maintenance burdens
  • Needs something he can trust architecturally

NetPad Journey:

  1. Finds NetPad on GitHub or Hacker News
  2. Inspects the repo: Next.js, TypeScript, MongoDBโ€”checks out
  3. Reads architecture docs, likes the patterns
  4. Tries the template gallery, impressed by variety
  5. Tests standalone exportโ€”confirms he can eject if needed
  6. Recommends to product team for internal tools

Success Metric: Confident it's a sound technical choice.


Journey 3: Healthcare Admin Needs Patient Intakeโ€‹

Scenario: Clinic manager needs digital patient intake forms to replace paper.

Current Pain:

  • Paper forms are slow and error-prone
  • Existing form builders don't handle HIPAA properly
  • Need data to flow to their MongoDB-based system

NetPad Journey:

  1. Finds NetPad via "MongoDB patient intake form"
  2. Sees Healthcare templates with relevant fields
  3. Appreciates self-hosted option for compliance
  4. Customizes Patient Intake template
  5. Enables conversational mode for patients who prefer chat
  6. Integrates with their MongoDB via connection vault

Success Metric: HIPAA-conscious digital intake in production.


Use Cases by Categoryโ€‹

Business & Salesโ€‹

  • Contact forms
  • Lead capture
  • Demo requests
  • Quote requests
  • Partnership inquiries

HR & Recruitmentโ€‹

  • Job applications
  • Employee onboarding
  • Time off requests
  • Performance reviews
  • Exit interviews

Healthcareโ€‹

  • Patient intake
  • Medical history
  • Appointment scheduling
  • Symptom checkers
  • Prescription refills

Financeโ€‹

  • Expense reports
  • Budget requests
  • Invoice submissions
  • Reimbursements
  • Audit questionnaires

IT & Operationsโ€‹

  • Help desk tickets
  • Bug reports
  • Feature requests
  • Asset checkout
  • Access requests

Eventsโ€‹

  • Event registration
  • RSVPs
  • Speaker submissions
  • Feedback surveys
  • Volunteer signup

Competitive Landscapeโ€‹

Direct Competitorsโ€‹

CompetitorStrengthWeaknessNetPad Advantage
RetoolMature, feature-richExpensive, complexMongoDB-native, simpler pricing
AppsmithOpen sourceGeneric, not data-focusedPurpose-built for MongoDB
BudibaseSelf-hosted focusLimited workflowBetter workflow automation

Adjacent Solutionsโ€‹

SolutionUse CaseNetPad Advantage
TypeformPretty formsMongoDB-native, workflows included
JotformSimple formsMore powerful, developer-friendly
ZendeskHelp deskNo per-seat pricing, customizable
Jira Service DeskIT ticketingSimpler, MongoDB-native
Custom devFull control30 min vs. 3 months

Our Positioningโ€‹

We are: MongoDB-native platform for internal tools

We are not: Generic form builder competing with Typeform

Key differentiators:

  1. MongoDB-native โ€” Not another integration to maintain
  2. "Build once, deploy twice" โ€” Same schema, traditional + conversational
  3. Open source + export โ€” True ownership, no lock-in
  4. Workflow automation โ€” Not just forms, complete automation

Messaging Frameworkโ€‹

Elevator Pitch (10 seconds)โ€‹

"NetPad lets teams build internal tools in 30 minutes instead of 3 months. It's MongoDB-native, so your data stays in one place, and you can export anytimeโ€”no lock-in."

Value Props by Audienceโ€‹

For IT Managers:

"Stop cobbling together Typeform, Zapier, and spreadsheets. NetPad gives you forms, workflows, and data management in one tool that connects directly to MongoDB."

For Developers:

"It's open source, architecturally sound, and you can export any app as standalone Next.js. If you outgrow NetPad, you're not locked in."

For Finance/Compliance:

"Self-hosted option keeps data in your environment. MongoDB-native means one source of truth for audits."

Headlines That Workโ€‹

  • "Build MongoDB Forms & Workflows Without Code"
  • "Internal Tools in 30 Minutes, Not 3 Months"
  • "MongoDB-Native. No Lock-In. Your Data, Your Way."
  • "From Form to Workflow to Production in Minutes"

Headlines to Avoidโ€‹

  • "The Best Form Builder" (we're not positioning as form builder)
  • "No-Code Revolution" (we're developer-friendly, not anti-code)
  • "Enterprise-Grade" (we're SMB-focused)

Current Go-to-Marketโ€‹

Distribution Channels (Active)โ€‹

ChannelStatusStrategy
Organic searchActiveTemplate pages, use case content
GitHubActiveOpen source discovery
Template galleryActiveConversion funnel, SEO
DocumentationBuildingDeveloper trust

Distribution Channels (Planned)โ€‹

ChannelStrategy
Hacker News"Show HN" with IT Help Desk tutorial
Dev.to / HashnodeTechnical tutorials
YouTubeWalkthrough videos
LinkedInCarousel posts for IT managers

No Active Paid Marketingโ€‹

We're focused on organic discovery initially. Paid campaigns are future consideration after:

  • Product-market fit confirmed
  • Pricing finalized
  • Onboarding optimized

Pricing (Draft)โ€‹

Note: Pricing model exists but will likely change before release.

TierPriceTarget
Free$0Individual, evaluation
TeamTBDSMB teams
EnterpriseTBDLarge orgs, compliance needs

Considerations:

  • 3-day free trial planned (all features)
  • No per-seat pricing (differentiator vs. Zendesk/Retool)
  • Self-hosted may have different model

Metrics We Care Aboutโ€‹

Activationโ€‹

  • Time to first form created
  • Time to first submission received
  • Template usage rate

Engagementโ€‹

  • Forms created per organization
  • Workflows created per organization
  • Conversational form usage

Retentionโ€‹

  • Weekly active organizations
  • Form submission volume over time

Growthโ€‹

  • Organic signups
  • Template gallery traffic
  • GitHub stars

Product Feedback Themesโ€‹

What we're hearing from early users:

ThemeFrequencyResponse
"Navigation is confusing"HighTier 1 priorityโ€”UX redesign
"Love the templates"HighExpanding template library
"Conversational forms are cool"MediumPolishing the experience
"Need more integrations"MediumRoadmap item
"Export feature is reassuring"MediumNeed better documentation

Questions for Product/Design Contributorsโ€‹

As you explore NetPad, consider:

  1. First impressions โ€” What confuses you in the first 5 minutes?
  2. Navigation โ€” Can you find what you need? Where do you get lost?
  3. Templates โ€” Which templates would you add? Which seem weak?
  4. Conversational forms โ€” Is the AI experience intuitive?
  5. Competitive gaps โ€” What would make you choose a competitor?

Your fresh perspective is valuableโ€”document what you observe.


Next Stepsโ€‹

  1. Explore the product: Create an account at netpad.io
  2. Try the template gallery: netpad.io/templates
  3. Test conversational mode: Pick a template and try "Conversational" tab
  4. Document your experience: Note friction points and ideas
  5. Share feedback: Open a GitHub discussion

Product context evolvesโ€”this document is updated as we learn.