Skip to main content
← Back to home
Live · 19d ago updated next refresh: due now
READ · choose how deep
NOCODE

Discourse Contact Forms

Moderately interested—Discourse admins want AI plugins but fragmentation and compatibility concerns persist.

The take: 3 complained · 1 willing to pay.
1 platforms · 3 mentions · ↑27 upvotes ·1 paid ·3 triggers
Opportunity score 49/100 Solid
NOCODE sector avg: 54 -5 Top 67% (12 cards)
GapMine track record: 254 predictions proven avg 34d early →
TimingBased on trigger event count, event freshness (14d window), and growth forecast. Percentile against all active cards.
50(moderate)
SeverityBased on pain intensity level, mentions (full-corpus percentile), and paid-evidence count (log scale).
60(moderate)
FeasibilityBased on existing supply count (inverse percentile — less supply = higher feasibility), build difficulty, and source diversity.
25(weak)
20d old Top tier Demand + Supply + Trigger all present
How we calculated this 49/100
50×30% + 60×45% + 25×25% = 48 → × 1.00 freshness → × 1.00 gold = 49
Final score discounts: freshness drops ~50% per week (20d old), and grade weight reflects how many of the 3 signal types (demand/supply/trigger) we found.
Dark Horse Has Pricing

Coverage confidence

We searched 4 of 3 places where competitors live — transparent about what we covered and what we missed.

Confidence
85% (High)
Where we searched
4 / 3 · GitHub · Reddit · App Store · Web Search
Real competitors found
1 shipped products (AI-verified from 66 raw matches)
Last scan
today · auto-refreshed every 2 weeks

Should you build this?

YES, if
  • You can ship in 1-2 weeks on $0-20/mo infrastructure
  • 1 signal of willingness to pay in the evidence pool
THINK TWICE
  • 5 competitors already shipping — crowded, harder to differentiate
VALIDATE THIS WEEK
  1. This weekend: DM 5 of the discourse users who complained — ask if they'd pay $9/mo for a fix (no build yet)
  2. Next 7 days: ship a 2-page landing site with $9/mo waitlist + "request beta" form — count signups
  3. If <10 signups in 7 days: kill it · the demand isn't there at this price

Updated as new signals arrive

Existing products · real complaints

Direct user quotes · 0 AI summarization

Discourse

"[discourse-meta] Contact Form" Broken in latest Discourse I recently updated Discourse and this plugin broke the site. (To be clear, this is more likely to be the result of my horri · discourse · ↑27 · original →

"[discourse-meta] How to force a topic to be edited by the user" Hi, we have members posting topics that are either incomplete, poor or AI generated. We want to be able to flag these and send it back to the creator, · discourse · ↑7 · original →

discourse-meta

(named in supply pool · no specific user complaint yet)

Sign in to see the full opportunity

Who this is for · Why now · Willingness to pay · Full timeline · Competitor landscape · Build with AI prompt · Validation playbook · Evidence pool · 8+ more sections

Sign up free →

Who is this for

developer (1) · indie-hacker (1) · support-engineer (1)

Bloomberg-style buyer profile · grounded in real signals

Pain · MEDIUM

"[discourse-meta] Contact Form" · discourse · ↑27 · original →

"[discourse-meta] How to force a topic to be edited by the user" · discourse · ↑7 · original →

"[discourse-meta] New ai docked composer" · discourse · ↑0 · original →

Willingness to pay

1 paid user · across 1 platforms

Full timeline · past → now → next

  • 2014-05 github License Source ↗
  • 2014-11 github File system dialogs Source ↗
  • 2015-10 github Old Link Dumps Source ↗
  • Now D1 3 active discussions · 1 paid evidence · 3 trigger(s)

Historical evidence from public discussions · filtered by relevance to this card

Future trend · next 7 days

Trend forecast becomes available once enough discussion history accumulates. Shown only when confidence >50%. New cards typically become predictable within 7-14 days after first sighting.

Competitor landscape 6

Grouped by source platform

Mentioned in discussions
discourse Auto-categorize topics using AI Source ↗
discourse Private Topics Plugin Source ↗
discourse Configure automatic backups for Discourse Source ↗

Build this with AI

We've assembled a full brief from the real evidence above. Ready to paste into any AI coding tool.

Or open in your AI tool: Claude ↗ · ChatGPT ↗ · Gemini ↗ · Perplexity ↗
~ 1-2 weeks · $0-20/mo infra
Preview what we send
I want to build a tool for: developer (1) · indie-hacker (1) · support-engineer (1)

The pain users describe: [discourse-meta] Contact Form

Timing / why now: [no explicit trigger]

Existing alternatives: Discourse

Help me draft an MVP technical plan:
1. Core user flow (happy path, 3-5 steps)
2. Data model (main tables and their key fields)
3. Tech stack recommendation (favor fast-to-ship options)
4. First 3 things to build this weekend
5. What NOT to build in v1 (scope discipline)

Context source: gapmine.com/opportunities/2026-04-30/discourse-plugin-compatibility

Prompt built by concatenating your real fields · 0 AI rewording · source link included for traceability

Build playbook · if validated ~1 week

Build only after VALIDATE THIS WEEK succeeds · Based on difficulty × medium and sector × nocode · curated playbook

1 Map full flow in Whimsical/FigJam first
2 Build in Softr/Glide on top of Airtable
3 Charge from day 1 · undercut existing tools
Sign up to save

Evidence pool 8

Grouped by signal type · click each source to verify

7 discourse1 aws
TRIGGER (2)
TRIGGER [discourse] [discourse-meta] Contact Form · Source ↗
TRIGGER [aws-whats-new] [aws-whats-new] Amazon DocumentDB (with MongoDB compatibility) is Now Available in the Canada West (Calgary) Region · Source ↗
SUPPLY (2)
SUPPLY [discourse] [discourse-meta] Auto-categorize topics using AI · Source ↗
SUPPLY [discourse] [discourse-meta] Private Topics Plugin · Source ↗
DEMAND (3)
DEMAND [discourse] [discourse-meta] Contact Form · ↑27 · med pain · developer · Source ↗
DEMAND [discourse] [discourse-meta] How to force a topic to be edited by the user · ↑7 · med pain · indie-hacker · Source ↗
DEMAND [discourse] [discourse-meta] New ai docked composer · med pain · support-engineer · Source ↗
PRODUCT (1)
PRODUCT [discourse] [discourse-meta] Auto-categorize topics using AI · Discourse · free · developer · Source ↗

This problem also appears in

Sample N=0 · canonical_need not yet mapped to other cards

Cross-card need mapping runs weekly. This card surfaces here once peers are clustered.

Updated weekly.

Topic hotness · weekly

Sample N=2 · need 6+ across 2 weeks

Weekly hotness surfaces once 6+ daily topic snapshots collected (3 in each week).

Updated daily at 07:00 UTC.

Signals last 14 days

Sample N=0 · need 3+ days

Sparkline shows once we have 3+ days of signals for this topic.

Momentum

How many readers are tracking or building this

0
saved by
0
builders

Be the first to watch — tap Save in the toolbar.

More in NOCODE