Question 1

Gameplan vs Raven — when do I run both?

Accepted Answer

**You typically run both.** They serve different conversation modes and reinforce each other:

**Raven (real-time chat):**
- Daily coordination — "who's around?", "can someone take this ticket?", "deploy is ready, watching"
- Quick questions with quick answers — typing in a DM or channel, expecting a response in minutes
- Casual social interaction — emoji reactions, GIFs, watercooler chat, team morale
- Notifications you act on within hours — incident alerts, customer escalations, on-call
- Best for: ephemeral, fast, social

**Gameplan (async discussions):**
- Project memory — every decision, design rationale, status update lives here forever, searchable
- Long-form thoughtful contributions — the kind of write-up that takes 15 minutes to compose and survives 6 months
- Structured project space — README, ongoing discussions, pages, tasks all under one Project Space
- Async-first contribution from team members in different time zones — no one feels bad about "missing" something because there's no synchronous pressure
- Knowledge base that grows over time — onboarding a new team member means giving them access to relevant Spaces
- Best for: durable, deep, structured

**Mithtech's standard Frappe-stack deployment** for clients in 25–250 person range: ERPNext + Frappe CRM + Frappe HR + Raven + Gameplan all running on a single Frappe bench. One database, one login, one backup, one permission model. Total incremental cost of adding Gameplan to a bench that already has Raven: typically ~₹0/month (no new infrastructure) + ₹60k–3 L Mithtech implementation for the Space architecture + culture migration.

**Distinction from chat-with-threading-pretending-to-be-async:** Slack/Mattermost/Raven *have* threading, but threads die after a few days as the channel scrolls past them. Gameplan threads stay; they're the primary unit of conversation, not a sidebar feature. This is the structural difference.

Question 2

Gameplan vs Discourse — Frappe themselves migrated, why?

Accepted Answer

Honest answer: **Discourse is excellent and Mithtech still recommends it for the right use case.** Frappe's internal move from Discourse to Gameplan wasn't about Discourse being bad — it was about getting closer Frappe-stack integration for internal team work specifically. The case for each:

**Discourse (still Mithtech's recommendation when):**
- The client wants a **public-facing community forum** for their open-source project, customer community, or product support discussions (think: ERPNext's own community.erpnext.com runs on Discourse).
- The use case has external participants who shouldn't have access to internal Frappe data.
- The forum needs SEO / public-search visibility.
- The client has Ruby + Postgres ops capability and is comfortable maintaining a non-Frappe app.
- Discourse's mature plugin ecosystem (BBcode / OAuth providers / bot integrations / SSO bridges) matters.

**Gameplan (Mithtech's recommendation when):**
- The client wants **internal team communication** — engineering RFCs, project discussions, OKR tracking, hiring panels, performance reviews — that should integrate tightly with their ERPNext / Frappe HR / Frappe CRM data.
- Same Frappe site means: identity unified with employees on Frappe HR, permission inheritance from Frappe roles, single login across all internal tools.
- The client doesn't want to maintain a separate Discourse stack alongside their Frappe stack.
- The Vue 3 + Frappe modern UX matters more than Discourse's Ember-based legacy front-end (Discourse's UX is functional but feels older).

**Frappe's specific reason for migrating:** they wanted Gameplan integrated with their internal Frappe HR (people, roles, departments) and ERPNext (projects, customers) data. Building Gameplan-as-a-Frappe-app gave them that integration; Discourse-as-a-separate-Rails-app couldn't.

Mithtech recommends matching the tool to the use case, not picking by tribal allegiance. We deploy both in production.

Question 3

Gameplan vs Notion / Basecamp / Linear — open-source vs SaaS trade-off?

Accepted Answer

**Notion** ($11–24/user/month for Business; ₹900–2,000/user/month) — beautiful product, broad scope (docs, wikis, project management, databases), rapid iteration. Trade-off: per-user fees compound at scale, data lives on Notion's servers (potential DPDP / GDPR / data-sovereignty concerns for regulated clients), no self-host option, no native ERPNext integration.

**Basecamp** ($99/team/month flat for Basecamp Plus, $299/year/user for Basecamp Pro Unlimited as of April 2026) — async-first philosophy explicitly shared with Gameplan; flat-rate pricing very team-friendly at scale; mature product with 25+ years of refinement. Trade-off: SaaS only, no integration with non-Basecamp tools, opinionated workflow that not all teams fit.

**Linear** ($8–14/user/month) — beautiful issue tracker / sprint tool primarily for software teams; opinionated about engineering workflows. Trade-off: scope limited to engineering work (not general team collaboration); per-user fees; SaaS only.

**Gameplan (Mithtech-deployed):** AGPL-3.0 open-source, free, runs on the client's existing Frappe bench (zero new infrastructure cost) or a small dedicated VPS (₹500–2k/month). No per-user fees. Implementation cost (Mithtech, one-time): ₹60k–3 L. Trade-off: smaller ecosystem than Notion (482 stars vs Notion's billion-dollar valuation funding their product team), narrower scope (focused on team discussions, not general docs/databases/project management), requires Mithtech ops if the client doesn't have Frappe expertise in-house.

**Mithtech's decision rule:**
- **Frappe-stack client wanting structured async discussions** → Gameplan
- **Cost-insensitive team wanting beautiful broad-scope SaaS** → Notion or Basecamp
- **Engineering-only team wanting tight issue tracking** → Linear
- **Public community forum** → Discourse

We don't push Gameplan when SaaS is the better economic answer for the specific team. For 25–250 person Frappe-stack teams the math overwhelmingly favours Gameplan; for 5-person teams Notion at ₹900/user/month is often cheaper than Mithtech's implementation cost amortised.

Question 4

What does Mithtech actually build and modify on top of Gameplan — modify, develop, deploy?

Accepted Answer

Mithtech is an expert Gameplan implementor — we **modify, develop, and deploy** the open-source platform. The Vue 40% + TypeScript 7.8% + Python 47.5% Gameplan codebase is exactly our team's daily Frappe + Vue 3 stack. AGPL-respecting — modifications stay in a separate Mithtech-owned Frappe app or use Frappe's official customisation surfaces, never as patches to upstream Gameplan source. Concrete scope from production deployments:

1. **Install + Frappe-site integration** — Gameplan deployed as a Frappe app inside an existing ERPNext / Marley / Frappe HR bench; Mithtech wires LDAP / OAuth / SAML via [Keycloak](/products/keycloak) for SSO across the entire Frappe stack.
2. **Space architecture design** — Team-level taxonomy (Sales / Engineering / Operations / Finance / HR), Project-level Spaces with consistent naming + permission policies, archival rules for completed projects, guest-access rules for external stakeholders.
3. **Custom Frappe Server Scripts** — auto-create Gameplan Discussions from DocType events: Sales Order won → Discussion in #wins Space; Project milestone reached → Discussion in the project's Space with auto-tagged participants; Quarterly Frappe Insights report generated → Discussion in #leadership with embedded charts; New hire's first day in Frappe HR → Discussion in #welcomes with onboarding-checklist Page; Production incident triggered (from Grafana alert via n8n) → Post-mortem Discussion auto-created in #incidents.
4. **Mithtech-built integration bridges** — Polygin Integration for WhatsApp digest of Gameplan activity to remote stakeholders; n8n workflows for cross-system event-to-discussion routing; Frappe Insights dashboards consuming Gameplan-activity metrics; Smartflo Integration for click-to-call from a Gameplan discussion to a CRM contact.
5. **Onboarding + cultural change support** — moving a team off WhatsApp / email / Slack-only into an async-discussion-first culture is *the hard part*, not the install. Mithtech provides team-training playbooks (90-minute workshops on async writing norms, decision documentation, RFC templates), example Project Space templates (sprint planning Space with backlog Page + retros Space + active-discussions area; OKR-tracking Space with quarterly goal Pages; hiring-panel Space with role-specific assessment templates), and ongoing facilitation support during the first 4–8 weeks of a team's Gameplan adoption.
6. **Migration from Discourse / Basecamp / Notion** — Discourse → Gameplan is well-trodden (Frappe themselves migrated). Basecamp + Notion exports require more transformation work; Mithtech-built scripts handle the structural mapping (Project → Space, Doc → Page, Comment thread → Discussion).
7. **Custom emoji + brand pack** — workspace branding (logo, colours), custom reaction emojis specific to the client's culture, branded notification templates.
8. **Backup architecture** — Gameplan data lives in the existing Frappe bench's database; Mithtech's standard Frappe-bench backup playbook (pgbackrest / xtrabackup / restic to S3-compatible storage) covers it. Quarterly restore drills documented and run.
9. **Observability** — Frappe Insights dashboards on Gameplan activity (most-active Spaces, discussion-velocity trends, member engagement, dormant-Space detection for archival); helps the client's ops team understand actual usage patterns and improve Space taxonomy over time.
10. **Performance tuning at scale** — for 100+ user deployments, RediSearch index tuning, Vue-frontend bundle optimisation, Frappe Realtime config for live-update efficiency.

Delivered as Mithtech-owned Frappe app + integration scripts + Space templates + onboarding playbook + runbook in the client's Git repository. Optional ongoing ops retainer for monitoring, version upgrades, ongoing facilitation as the team grows.

Frappe Gameplan — Async Discussions for Remote Teams

What can Frappe Gameplan do?

AGPL-3.0 · 482+ GitHub stars · 228 forks · actively maintained · maintained by Frappe Technologies (the ERPNext team)

How does Frappe Gameplan work?

Audit & scope

Deploy on your infrastructure

Customise & integrate

Train & roll out

Operate & evolve

Frappe Gameplan vs the alternatives

Estimate your savings with Frappe Gameplan.

Frequently asked questions about Frappe Gameplan

Get Frappe Gameplan running in weeks, not quarters.

Products that pair with Frappe Gameplan — Async Discussions for Remote Teams

Pulse — Agile Delivery on ERPNext

Mattermost — Self-Hosted Team Collaboration + Boards

NTFYnext — Push Notifications for Frappe

ERPNext

Frappe HR

Frappe Insights

Know your budget? Plan your Frappe Gameplan — Async Discussions for Remote Teams stack.

Frappe Gameplan — Async Discussions for Remote Teams

What can Frappe Gameplan do?

AGPL-3.0 · 482+ GitHub stars · 228 forks · actively maintained · maintained by Frappe Technologies (the ERPNext team)

How does Frappe Gameplan work?

Audit & scope

Deploy on your infrastructure

Customise & integrate

Train & roll out

Operate & evolve

Frappe Gameplan vs the alternatives

Estimate your savings with Frappe Gameplan.

Frequently asked questions about Frappe Gameplan

Gameplan vs Raven — when do I run both?

Gameplan vs Discourse — Frappe themselves migrated, why?

Gameplan vs Notion / Basecamp / Linear — open-source vs SaaS trade-off?

What does Mithtech actually build and modify on top of Gameplan — modify, develop, deploy?

Is Frappe Gameplan — Async Discussions for Remote Teams free and open source?

Can Frappe Gameplan — Async Discussions for Remote Teams be self-hosted on your own server?

What integrations does Frappe Gameplan — Async Discussions for Remote Teams support?

How does Mith Tech implement Frappe Gameplan — Async Discussions for Remote Teams for businesses?

Gameplan vs Raven — when do I run both?

Gameplan vs Discourse — Frappe themselves migrated, why?

Get Frappe Gameplan running in weeks, not quarters.

Products that pair with Frappe Gameplan — Async Discussions for Remote Teams

Pulse — Agile Delivery on ERPNext

Mattermost — Self-Hosted Team Collaboration + Boards

NTFYnext — Push Notifications for Frappe

ERPNext

Frappe HR

Frappe Insights

Know your budget? Plan your Frappe Gameplan — Async Discussions for Remote Teams stack.