Send feedback

Why your feedback matters

Businesslogic is shaped by the people who use it. If something is confusing, missing, or could work better — from the way you map inputs and outputs to the documentation, the integrations, or the pricing — we want to hear it. Concrete examples are especially useful: tell us what you were trying to do, what you expected, and what actually happened.

Feature ideas are just as welcome. Many of the capabilities in the product today started as a single message from a user. We read every submission, and while we cannot promise to build everything, your input directly influences what we prioritise next. If your note needs a reply, leave an email address and we will get back to you within a couple of business days.

What happens next

Every submission lands with the team that builds Businesslogic — not a black hole. We group recurring themes, weigh them against what we are already working on, and let the common requests shape the roadmap. Small fixes and wording changes are often handled within a release or two; larger feature ideas are logged and revisited as we plan ahead.

If you are blocked right now rather than sharing an idea, the contact form reaches us the same way but flags that you need a reply. Looking for a how-to instead? The API documentation and the blog answer most setup questions, from publishing your first Excel API to wiring it into Make.

What kind of feedback helps most

All feedback is welcome, but a little structure makes it far easier for us to act on. If you can, tell us three things: what you were trying to do, what you expected to happen, and what actually happened. A concrete example — the workbook you were publishing, the field you were mapping, the integration you were wiring up — turns a vague impression into something we can reproduce and fix.

• Bugs and rough edges. Something broke, behaved unexpectedly, or was harder than it should have been. Steps to reproduce and a screenshot help us move quickly.
• Confusing wording or docs. A label, an error message or a documentation page that sent you the wrong way. Tell us where you got stuck and what you assumed it meant.
• Missing capabilities. A function, an integration or an option you needed and could not find. Describe the outcome you were after, not just the feature — it often points to a simpler solution.
• What is working well. Knowing which parts genuinely save you time tells us what to protect as the product grows.

You do not need polished prose — a few honest sentences are plenty. Every note is read by the people who build Businesslogic, and the patterns we see across many messages are what shape the roadmap. If you would like a reply, leave an email address and we will follow up within a couple of business days.