GopherCRM implementation and customisation, in an environment you control

Start with a short, free conversation. If there's a fit, the next step is a fixed-fee analysis of one workflow, paid before it starts. Implementation is quoted separately.

Request a free qualification call
No payment is taken on this page, and a request commits you to nothing.
Explore the open-source GopherCRM project

How it works

Free
1

Send your request.

Tell us what you need and what you use today.

2

Short free conversation.

We check your workflow, constraints, essential integrations and who would operate the system. It isn't a written recommendation or a demonstration.

Paid before work starts
3

Scoped analysis, paid before it starts.

If there's a fit, we agree a written scope and a fixed fee. You accept the scope and terms, and work starts once we have verified your payment.

4

Your written result.

You get a workflow and requirements map, a fit assessment that includes alternatives, data and integration requirements, gaps and risks, acceptance criteria, and an implementation scope and estimate. A named person at Magendoo reviews it and takes you through it.

Separate decision
5

Your decision.

Implementation, customisation and optional care are quoted separately, and you don't have to buy them from us. The analysis can recommend against GopherCRM.

What the analysis gives you

The analysis covers one named workflow and ends in a clear recommendation: proceed with GopherCRM, proceed only if named conditions are met, use another solution, or leave things as they are for now. All of these are valid results, and the fee is the same whichever one we reach.

You receive

  • A map of the current and target workflow, with owners and handoffs
  • A requirements register, with a business reason for each item
  • A fit check of your must-haves against an exact GopherCRM build, compared with up to two alternatives and with keeping your current tools
  • Data and integration requirements
  • Gaps and risks, including who would own hosting, updates, backups and support
  • Acceptance criteria that could be tested later
  • An implementation scope and estimate, which is not a fixed price or a delivery date
  • A recommendation and a readout, with one revision round for factual errors and misunderstood requirements

Not included

  • Installation, a pilot, a demo environment, configuration or code
  • Data migration or live integration tests
  • A binding implementation quote or a reserved start date
  • Legal, tax or GDPR advice, security certification or penetration testing
  • Care or support after the readout
Request a free qualification call

If you go further: implementation and care

Each of these is a separate decision with its own written quote. None is included in the analysis fee.

Implementation.

Deployment in your environment, configuration around the agreed workflow, data import where scoped, tests against agreed acceptance criteria, and training for the people who will use it.

Customisation.

Changes to fields, screens, rules and workflows. Because the code is open, work can go beyond configuration where that is justified.

Integrations.

Connections to the systems your team depends on, such as a website, email or ERP. We inspect the systems first. An integration named here is something we can scope, not something that already exists.

Optional care.

Agreed responsibility for updates, backups, restore checks and support. Coverage is written into the agreement. You can also run the system yourself.

Handover.

Code, documentation, access and a runbook, so your team or another supplier can take over.

You are buying services and an agreed result. This is not a subscription to a shared CRM hosted by Magendoo. We confirm who would deliver and our capacity for each project, so a request or an analysis does not reserve a start date or guarantee an implementation quote from us. Hosting and third-party services are priced separately.

What GopherCRM covers today

GopherCRM is an open-source CRM built with Go and React. Its public project documentation describes:

  • leads, customers, companies and deals on a five-stage pipeline
  • products and quotes
  • support tickets and tasks
  • embeddable lead-capture forms with spam protection
  • admin-defined follow-up rules
  • admin, sales, support and customer roles, and a REST API

GopherCRM is still evolving, and the project documentation lists known limitations. We raise any limitation we already know affects you in the free conversation, and the analysis checks your must-haves against the exact build.

When it fits, and when something else fits better

GopherCRM may suit you if:

  • you are a small team with one clear path from enquiry to deal to support
  • you need changes to the system itself, and want code that can be adapted
  • you can name who will own hosting, backups and support, whether that is your team or a supplier
  • your team can work in an English interface. The project does not document a translation framework today, so translation would be separate scoped work

Another option may suit you better if:

  • You want a CRM running without anyone operating it. A hosted CRM is likely to be simpler.
  • You need a broad ERP programme. Consider Odoo. Magendoo also provides Odoo implementation, so we have an interest in that recommendation and will say so.
  • Your needs are met by configuring an established open-source CRM. Compare EspoCRM or Frappe CRM. Self-hosting and open source are not unique to GopherCRM.
  • Your current tools work once ownership is clearer. Then keep them. We will tell you if we think that is the case.

If the free conversation already gives the answer, we say so and don't sell you an analysis.

Enterprise requirements get their own scope

Need SSO, user provisioning, audit evidence, retention controls or a specific infrastructure boundary? Tell us which of these your procurement and operations teams treat as mandatory. The analysis can check them against a named build and say what is available, what needs validating and what would need development.

These are requirements we can assess. We are not claiming a ready-to-deploy enterprise edition with these controls.

→ Discuss enterprise requirements

Questions

The first conversation is free. The analysis has a fixed fee set for the scope we agree, and you see it in writing before you accept. It's paid in full before work starts. Implementation is quoted separately once the scope is known. We don't publish a package price, because scope varies.
It gives you a decision and a scope you can act on before you commit to a system or supplier. It uses people's time to check your workflow, requirements, data, integrations and risks, and it stays useful if the answer is a different product.
Not on this page. After you accept the written scope and terms, we send an invoice or an agreed payment request. Work starts once we have verified your payment in full.
The first conversation needs no system access, and please don't send passwords, customer records or confidential documents. The standard analysis uses counts, field lists and anonymised samples rather than production access or real customer datasets.
It depends on scope and on our capacity at the time. The working window for an analysis is stated in its written scope and runs from verified payment. Implementation timing is part of any separate quote.
No. Any implementation is a deployment in an environment you control. Hosting and care are agreed separately.
Possibly. The analysis records the data and interfaces involved and what would need validating. Migration and integrations then need their own scope and are not included automatically.
The free conversation isn't a demonstration, and the standard analysis doesn't include a demo environment. The public project documentation is open to read. Tell us which workflow you want to see and we will confirm whether a suitable demonstration is available. It would use test data. Our own enquiry CRM is not used as a public demo.
Not for this service yet. GopherCRM may not be right for you, and the analysis exists to find that out.
No software does that alone. Compliance depends on how the system is configured and operated, and on your own policies. We can scope hosting location, access, retention and deletion requirements with you, but we do not give legal advice or certify compliance.
Magendoo is based in Romania and works with EU businesses, in English.
The GopherCRM core is published under the MIT licence. Any implementation agreement sets out the code, documentation and access handed over, and identifies any third-party terms that apply.

Request a free qualification call

Tell us what you need. We'll review it and reply by email if there looks to be a fit. A request commits you to nothing and doesn't book a call. If there's a fit, the next step is a paid analysis, which we'd scope and agree with you first.

Email info@magendoo.ro for details.