Support

Get help with Laimonade

Whether something broke, something confused you, or the product got in your way — here is how to reach us, and the answers to the questions we hear most.

Email support

The channel of record. Include the project name and, for anything that went wrong, what you expected to happen — we aim to answer within one business day.

support@laimonade.com

Documentation

Setup, the sprint workflow, connecting a coding agent over MCP, and a troubleshooting guide for the failure modes we already know about.

TroubleshootingGetting startedAll documentation

Chat with Laimon — coming to this page

We are bringing Laimonchat here, so support starts as a conversation with Laimon: it knows the documentation and can look at your question before a person needs to. Until it ships, email reaches the same team.

Frequently asked questions

The questions existing users hit. If yours is about whether Laimonade fits your team in the first place, the homepage FAQ answers those.

How do I contact Laimonade support?

Email support@laimonade.com. Include the project name you are asking about and, for anything that went wrong, what you expected to happen — that is usually all we need to reproduce it. Every message is read by the team that builds the product; there is no tier of support to get past first.

How fast will I get a reply?

We aim to answer within one business day. We are a small team based in Antwerp, Belgium, so replies land on Central European business hours. Messages that describe a blocking problem — you cannot reach your board, or your agents cannot fetch work — are answered first.

How do I report a bug?

Email support@laimonade.com with what you did, what you expected, and what happened instead. A screenshot or the exact error text shortens the round trip considerably. If a coding agent hit the problem over MCP, include the tool name it called and roughly when — each connector action is recorded with its outcome, so a timestamp lets us find the exact call.

My coding agent cannot connect over MCP. What should I check first?

Check three things in order: that you are signed in to Laimonade in the assistant you connected, that the connection was granted access to the project you are asking about, and that the agent is calling a tool that exists — the tools reference lists every one. The troubleshooting guide walks through the common failure modes; if you get through it without a fix, email support with the error the agent reported.

TroubleshootingMCP tools referenceConnect your coding agent

Laimon stopped doing AI work mid-month. Is something broken?

Most likely you have used the month’s AI credits: when they run out, Laimon stops taking new token-backed work rather than billing you for more. The board, the backlog and the MCP connection keep working — it is the AI work that pauses, not your access. Credits reset monthly and do not roll over; if you hit the ceiling regularly, a larger plan differs only in credits, never in features.

Pricing

I have a billing question. Who do I ask?

The same address: support@laimonade.com. Plans are priced per project rather than per seat, so invoices scale with projects, not with people you invite. You can cancel at any time and cancellation takes effect at the end of the current billing period — nothing is charged beyond it.

PricingTerms of service

Can I ask for a feature, or tell you the product is wrong about something?

Yes, and we mean it: the roadmap is shaped by what design partners and customers report, not by what we guess. Email support@laimonade.com with what you were trying to do and where the product got in the way. "Laimon grooms items in a way my team keeps rewriting" is exactly the kind of message we want.

Contact

How do I get my data out, or deleted?

You keep ownership of the content you submit — the terms of service say so explicitly — and the privacy policy sets out how long information is retained and your right to ask for its deletion. Email support@laimonade.com to exercise either; deletion requests are handled under the policy, not at our discretion.

Privacy policyTerms of service