Melta
Who it is for
Melta for teams inside companies - internal tools without waiting for IT
For teams in operations, HR, product and field service that need an internal tool of their own: approvals, task boards, time tracking, a helpdesk, a small CRM. You describe the workflow in plain words, Melta builds the tool with accounts and roles, you test it with your team in the preview and take it live. After that, a change is a chat message, not a ticket.
Where you are today
Your team has a workflow that lives in spreadsheets, chats and email threads: requests someone has to approve, tasks that get handed out again every week, hours pieced together at month end, enquiries that land in one person's inbox. Everyone knows a dedicated tool would help. IT has it on the list, but the list is long, and off-the-shelf software either does not fit your workflow or costs more than the case justifies. That is where Melta comes in: you describe how your workflow works and get a complete tool that Melta builds, puts online and runs - without a developer budget, a server or a maintenance contract.
What Melta builds for you
Every tool comes with logins including registration, password reset and email confirmation, the roles your workflow needs, its own database separated from every other product, and email sent under the tool's name. A few examples:
Approvals and requests
Leave, expenses, purchases, access: the person requesting sees where it stands; the approver gets an email and decides with one click. Every decision stays traceable, with date and person.
Weekly task boards
A board where the team plans, assigns and ticks off tasks - like the example product TeamTakt, which organises a team's tasks week by week.
Time tracking
Hours per project and person, tracked with a timer or entered afterwards, plus a monthly overview for the team lead. Roles separate who records and who reviews. More on the time tracking page.
Helpdesk and small CRM
Enquiries from the team or from customers with status, owner and history; for field service, contacts, appointments and notes in one place. Incoming mail lands in the support inbox and is sorted automatically. More on the CRM page.
The cards are a selection. The concept describes your tool exactly, with the fields, roles and steps you really need. More on accounts and roles on the user accounts page.
How it works
- Describe - You explain in your own words how your workflow runs today and what the tool should do: who requests, who approves, what happens every week. Melta asks up to four clarifying questions, none of them technical.
- Read the concept - From that comes a concept in plain language: pages, roles, flows. You share it with the team, collect feedback and change it by chat until it fits.
- Have it built - When you approve, the build starts, paid from the credits of your plan. Melta builds the complete tool - interface, logic, accounts, database, email, legal pages - typically within 24 hours. You get an email when it is done.
- Pilot in the preview - The private preview comes seeded with demo data and named test logins. A small group from the team walks through the workflow in every role before the rest of the company hears about it.
- Go live - Once the pilot has convinced you, the tool goes live in seconds, without a rebuild. Before that, Melta checks that the operator details for the imprint are complete. You choose which preview data to carry over; the previous live version stays available for a rollback.
- Change by chat - "Add a field for the cost centre", "Make the approval two-step": you send it to your product's editor, watch it work, step in if needed and deploy the change to preview or live.
More on the preview and live and chat editor pages.
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
We have no IT capacity. Who runs the tool?
Melta does. Hosting on a globally distributed network, a database of its own per product, TLS, email, legal pages, a support inbox, error monitoring and analytics are part of the plan. There is no server for anyone to look after and no maintenance contract.
Can we test with a small group first?
Yes. Every product has a private preview with demo data and named test logins. A pilot group walks through every role there. The tool goes live only when you decide - in seconds, without a rebuild, and you choose which preview data to carry over.
How do change requests from the team get into the product?
As a chat message to your product's editor. You watch it make the change, can steer or stop it mid-run, and the preview updates live. When it fits, you deploy the change to preview or live from the chat. Change runs are included in every plan.
Is our data separated from other products?
Yes. Every product runs in isolation with its own database. The accounts, roles and data of your tool belong to that one product. Which roles exist and who sees which data is set in the concept - and you change it by chat later on.
Describe your workflow. Melta builds the tool.
A concept uses only a few credits. The tool is built, piloted and run once you approve it - with accounts, roles and a database of its own.
Get early access