Examples

Build a CRM with Melta - contacts, deals and follow-ups in a product shaped to your team

For sales teams, consultancies, agencies and small businesses that want contacts, enquiries and closed deals in one place without getting lost in a large suite. You describe how you work with your customers. Melta builds a CRM with exactly your stages, fields and roles, puts it online and runs it.

What a product like this can do

A CRM is your team's memory: who is who, where each deal stands, what was last discussed, what comes next. These building blocks belong to it, in the shape your concept defines:

Contacts and companies

People with role, phone, email and notes, linked to their company. A company shows all its contacts and open deals.

Deals in stages

First call, proposal, negotiation, closed - or the stages you really use. Every deal has a value, a contact and an owner.

Activities and notes

Calls, meetings and notes land on the contact, in order. Whoever takes over reads the history.

Reminders and tasks

Follow up in three days, proposal by Friday: tasks hang on a contact or a deal, with a due date and an owner.

Email from the product

A message to a contact goes straight out of the CRM, under your product's name. Replies land in the support inbox.

Simple reporting

Open deals per stage, deals closed this month, activities per person. The numbers for the weekly meeting, no more.

Import of your contact list

Your existing list from a spreadsheet or an old tool comes along. In the concept you describe which columns it has.

Roles for your team

Sales sees its own deals, management sees all of them, the assistant keeps contacts tidy. Who sees what is set in the concept.

A CRM for one team instead of a suite for everyone

Large CRM suites are made for every industry at once: hundreds of fields of which you need five, stages from somebody else's sales process, settings someone has to maintain. In the end the team bends to the tool, and the spreadsheet next to it lives on.

With Melta you describe your process in your own words: which stages a deal goes through, what you need to know about a contact, who may see what. The CRM then has exactly these fields, stages and roles. What is missing comes later by chat; what you do not need is simply not there.

A CRM is not yet among the example products. The closest is TeamTakt, an example product for weekly team tasks made of the same building blocks: accounts with roles, lists with owners, reminders, email - just with weekly tasks instead of contacts and deals at the centre.

How Melta builds it

  1. Describe - You explain how you handle enquiries and customers today, which stages a deal has and who works with it. Melta asks at most four clarifying questions, none of them technical.
  2. Read the concept - From that comes a concept in plain language. You change it by chat until it matches your everyday work.
  3. Approve and let it build - When you approve, the build starts, paid from the credits of your plan. Melta builds the whole product - interface, logic, accounts, database, email - typically within 24 hours. You get an email when it is done.
  4. Test in the preview - The private preview comes seeded with demo contacts and deals and has named test logins per role. You walk a deal from enquiry to close.
  5. Go live - Going live takes seconds, with no rebuild. Before that Melta checks that your operator details for the legal pages are complete. You choose which preview data to carry over, and you can roll back to the previous live version.
  6. Change by chat - A new field, an extra stage, a different report: you write it to your product's editor, watch it work, can steer or interrupt, and the preview updates live. Change runs are included in every plan.

What comes with it

Your CRM runs on a melta.ai subdomain or, from the Growth plan, on your own domain, bought through Melta or connected. Emails to contacts go out under your product's name, and replies land in the support inbox, which sorts incoming mail automatically. Imprint, privacy policy and terms are generated from your operator details for Switzerland, Germany and Austria - a general basis, not legal advice. On top of that: analytics without cookies, error monitoring and protection against spam on logins and forms. If your CRM should one day sell something, say as a subscription for other businesses, payment processing is part of the platform too. There is no maintenance contract.

You own what runs.

What it costs

A concept uses only a few credits; afterwards your product runs on a plan per organisation with credits every month. All numbers and how the price is made up are on the pricing page.

Common questions

Has Melta already built a CRM as an example product?

Not yet. The closest is TeamTakt, an example product for weekly team tasks: accounts, roles, lists with owners and reminders. A CRM is made of the same building blocks, with contacts and deals at the centre instead of weekly tasks.

Who can sign in to my CRM?

The people you plan for in the concept. Every product comes with registration, password reset and email confirmation, plus the roles your process needs, for example sales, management and assistant. The team members of your Melta plan are separate: they edit the product inside Melta.

Can I bring my existing contact list?

Yes, if you describe the import in the concept: which columns your list has and how they map to contacts and companies. The build puts it in place, and you check it in the preview before anything goes live.

What does a CRM cost if it sells nothing?

The share of sales applies only when your product sells something; an internal CRM does not, so neither a share nor card processing is due.

Describe how you work with customers. Melta builds the CRM to match.

A concept uses only a few credits. Your CRM is built, put online and run once you approve it - with accounts, roles, email and legal pages.

Get early access