Examples

Build a project and task management tool with Melta - the way your team works

For teams, businesses and founders who want to run their projects and tasks in a tool of their own instead of bending to a large one. You describe how your team works: which projects there are, who takes on tasks, in what rhythm you plan. Melta turns that into a complete product, puts it online and runs it.

What a product like this can do

A project and task management tool answers the same question every day: who does what by when, and where do we stand? Which building blocks your product gets for that is written down in the concept. These are the typical ones:

Projects

Every project has its own space: goal, people involved, tasks, status. Whoever opens it sees at a glance what is open and what is stuck.

Boards and lists

Tasks as columns from Open to Done or as a sortable list, depending on how your team thinks. Both views show the same tasks.

Tasks with an owner

Every task has a responsible person, a due date, a checklist for sub-steps and comments right on the task. No task belongs to nobody.

Weekly rhythm

A "This week" view shows what is due and who takes it on. The team starts Monday with it and closes the week on Friday.

Notifications by email

A new assignment, a deadline coming closer, a comment on your task: your product sends the mail under its own name. Replies land in your support inbox.

A simple timeline

Projects and milestones side by side on one time axis, so overlaps become visible before they turn into a problem.

Roles

Admin, member, guest. Admins set up projects and the team, members work on tasks, guests such as clients or freelancers see only the project they were invited to.

A tool of your own instead of a large project suite

The large project tools are built for teams with project managers, sprints and reports; for a small business, an agency or a founding team they are often too much. A product of your own maps exactly the workflows you have, in your own words and without ballast, and it belongs to you, with your own domain and your own data.

How small such a tool may be is shown by the example product TeamTakt: weekly team tasks for teams of 2 to 10 people, with due dates, owners, comments on the task and a weekly overview at its heart. Melta has not yet built a full project and task management tool with boards, a timeline and a guest role as an example product; TeamTakt is the related example of how a task tool grows out of a description in plain language.

How Melta builds it

  1. Describe - You tell it in your own words how your team works: which projects there are, who takes on tasks, whether you plan weekly, whether clients should be able to read along. Melta asks up to four non-technical follow-up questions.
  2. Read the concept - From that comes a concept in plain language: which pages exist, what happens on each, which roles there are. You change it by chat until it fits.
  3. Confirm and have it built - When you confirm, the build starts, paid from the credits of your plan. Melta builds the product: interface, logic, accounts, database, emails, legal pages. Typically within 24 hours; you get an email when it is done.
  4. Preview with test logins - The finished product runs in a private preview with demo projects and named test logins for admin, member and guest. You click through it the way your team will later.
  5. Go live - In seconds, with no rebuild. Before that, Melta checks that your operator details for the imprint are complete. You choose which preview data comes along, and you can roll back to the previous live version if needed.
  6. Keep developing by chat - "Add a field for effort", "guests should be able to comment": you write it in the editor's chat, watch it being done, can steer along the way, and deploy the result to the preview or live. Change runs are included in every plan.

What comes with it

Accounts with registration, password reset, email confirmation and the roles from your concept are built in, on a database of its own, isolated from every other product. If you sell the product as a subscription, payment processing is included: your customers see your product as the merchant, payouts go to your bank account, and you need no separate contract with a payment provider. Emails go out under your product's name, replies land in the support inbox, which sorts them automatically. On top of that come imprint, privacy policy and terms generated from your operator details for Switzerland, Germany and Austria (general information, not legal advice), a melta.ai subdomain or, from the Growth plan, your own domain, cookieless analytics, error monitoring and protection against spam on logins and forms. Hosting is globally distributed, with no server to manage and 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 project management tool as an example product?

Not yet. The closest is the example product TeamTakt: weekly team tasks for teams of 2 to 10 people, with due dates, owners, comments and a weekly overview. You describe a product with projects, boards, a timeline and a guest role in the same plain language, and Melta builds it from your concept.

Can I use the tool only for my own team, without selling anything?

Yes. Then you need the one-time build and a plan for your organisation, nothing more. The share of sales applies only when your product sells something. If you later want to offer it to other teams as a subscription, payments with one-time purchases and subscriptions are already part of the platform.

Can clients or external freelancers work in it?

Yes, through the guest role. Guests see only the projects they are invited to and can do only what the concept sets out for them, for example read and comment on tasks but not create projects. Roles and rights are defined in the concept and changed later by chat.

What happens to the demo projects from the preview when I go live?

At go-live you choose which preview data comes along; it is merged by type. You usually leave demo projects and test logins behind and start live with your real team. The preview stays as its own environment.

Describe how your team works. Melta builds the tool for it.

A concept uses only a few credits. The product is built, put online and run as soon as you approve it - with accounts, roles, emails and legal pages.

Get early access