Private workflow tools
Provide the inputs, rules, exceptions, and output your process requires. Motifuse can turn that defined workflow into a focused web tool for you or approved users.
Commission Review Tool
Private workspaceExport report1Upload sales data
sales_export_jan_2026.csv24,532 records
2Apply rules
3Exceptions to review
Results
Total payouts
$128,450.75
Generate report
Last run 2 min agoCompleted
Where a private tool sits
Two of these cost nothing to try. Read them before commissioning a build — the review checks them first anyway.
Common one-off tasks in the browser. No sign-up, and each tool states how it handles your data.
Best for: an occasional task anyone would do the same way.
Explore free toolsMaintained products for recurring document and data work, used from your workspace account.
Best for: a workflow a maintained product already covers.
View productsA tool built around your documented inputs, rules, exceptions and output, restricted to approved users.
Best for: a repeated process no public tool can express.
Describe your workflowPositioning
A private tool solves one described process end to end. It is specified from the work you already do, not from a feature list, and its boundaries are written down before anything is built.
Each of these is settled in writing before development starts, not discovered during the build.
If your request resembles one of these, the review will say so and point you at a better path instead.
The anatomy of a private tool
Every private tool is scoped against these five questions. A request that answers them is enough to begin a review.
Files, records, user selections, or structured form data.
What arrives, and in what shape?
Calculations, mappings, validation, formats, thresholds and business conditions.
What decides the result?
Missing information, conflicts, unusual values, or items that require review.
What must a person still look at?
Reports, transformed files, calculations, documents, summaries or exports.
What does finished look like?
Approved users, private workspace, retention rules and the delivery model.
Who may use it, and where does it live?
What a private tool can be
Illustrative scenarios showing the shape of a suitable request — inputs, rules, exceptions, output. Not customer case studies.
Calculate commissions using role-specific rates, thresholds and caps. Flag exceptions for review.
Illustrative scenarios. They describe the kind of workflow that suits a private tool, not projects delivered for a named customer.
Convert spreadsheets or files into structured data with mapping, validation and clean exports.
Illustrative scenarios. They describe the kind of workflow that suits a private tool, not projects delivered for a named customer.
Create branded quotes, contracts or letters using rules, templates and live data.
Illustrative scenarios. They describe the kind of workflow that suits a private tool, not projects delivered for a named customer.
Submissions, validations and reviews with status tracking and audit-ready records.
Illustrative scenarios. They describe the kind of workflow that suits a private tool, not projects delivered for a named customer.
Match data from two sources, highlight differences and export a resolution report.
Illustrative scenarios. They describe the kind of workflow that suits a private tool, not projects delivered for a named customer.
Domain-specific calculations with business rules and scenario comparisons.
Illustrative scenarios. They describe the kind of workflow that suits a private tool, not projects delivered for a named customer.
Before you request
The more of these that describe your situation, the more likely a private tool fits.
Recognise most of these? Describe the workflow and the review will confirm whether a private tool is the right shape for it.
Describe your workflowFor a common, occasional task where nothing needs to be saved and no private rules apply.
Explore free toolsWhen a maintained product already covers the workflow, adopting it is faster and cheaper than commissioning a build.
View productsWhen the rules are still incomplete, several systems must connect, or sensitive data is involved, defining the requirement is the first piece of work.
Start a requestPublic vs product vs private
The free collection stays free and unchanged. These are the differences that affect a decision.
| What matters | Free public tools | Motifuse products | Private tools |
|---|---|---|---|
| Intended audienceKey | Free public toolsEveryone | Motifuse productsAnyone with a Motifuse account | Private toolsYou or the users you approve |
| AccessKey | Free public toolsPublic, open access | Motifuse productsAccount sign-in for saved work | Private toolsSign-in required, scoped to your account |
| Rules & logicKey | Free public toolsGeneral-purpose | Motifuse productsThe product's own model | Private toolsBuilt around your documented rules |
| Branding | Free public toolsMotifuse branding | Motifuse productsMotifuse branding | Private toolsYour branding when the scope includes it |
| Inputs & outputs | Free public toolsStandard formats | Motifuse productsThe formats the product supports | Private toolsThe formats your process requires |
| Saved state | Free public toolsUsually not saved | Motifuse productsSaved to your workspace | Private toolsSaved only when the scope calls for it |
| AdvertisingKey | Free public toolsMay include ads | Motifuse productsNone inside the workspace | Private toolsNone inside the workspace |
| Support | Free public toolsHelp pages and contact form | Motifuse productsProduct documentation and help | Private toolsDirect support during the agreed period |
| Hosting | Free public toolsMotifuse shared infrastructure | Motifuse productsMotifuse infrastructure | Private toolsThe delivery model agreed for your project |
| Maintenance | Free public toolsBest-effort | Motifuse productsMaintained as part of the product | Private toolsIncluded only when the agreement says so |
| Ownership & licence | Free public toolsNo ownership transferred | Motifuse productsMotifuse owns it; you use it | Private toolsDefined in your project agreement |
| Pricing | Free public toolsFree | Motifuse productsPublished plan for that product | Private toolsEstimated per project after review |
| Updates | Free public toolsImproved at Motifuse's discretion | Motifuse productsProduct roadmap | Private toolsChanges go through a change request |
| Data handling | Free public toolsStated on each tool page | Motifuse productsStated in the product documentation | Private toolsAgreed before development begins |
KeyKEY marks the differences that most often decide which path a visitor actually needs.
Hosting, ownership and maintenance vary by project and are set in your written agreement rather than by a standing package.
Where a private tool lives
Three delivery models are available. Which one applies is confirmed during scoping — based on who needs access, where the data may go, and how much you want to run yourself.
Delivered inside the Motifuse workspace and opened from a browser after sign-in.
Runs on your own domain or environment instead of the shared Motifuse workspace.
The build is handed over for you or your own team to run and continue.
Handover, source-code rights and licensing are included only when the written agreement for your project says so. They are not implied by any of these models.
Commission Review Tool
In developmentMTP-2026-000018
Your tools
Delivered tools appear here once a project reaches delivery.
How we work together
Six stages, each with an approval point. No stage begins because the previous one finished — it begins because you agreed to it.
You describe the process in plain language. A specification document is not required.
You confirm the summary reflects the real process.
Every request is read by a person and assessed before any estimate is prepared.
We tell you if a free tool or an existing product fits better.
What will be built, what is excluded, and what drives the cost are written down.
Nothing is built until you accept the scope and the estimate.
The screens, states and validation are agreed before implementation begins.
You approve the flow before the build starts.
The tool is built and exercised against representative data, including exception cases.
You test it and raise changes before acceptance.
The tool is deployed under the agreed model, access is configured, documentation is handed over.
Acceptance is recorded against the agreed scope.
Submitting a request is free and does not commit you to anything. As the request form states, submission does not guarantee project acceptance or confirm final pricing.
Boundaries
Ambiguity here is what turns a small build into a dispute. These lists are the starting position; your written scope decides.
Part of a normal build at no extra line item.
Ordinary commercial items, quoted on their own.
Requests Motifuse will not take on.
This page describes the usual position. The written scope or agreement for your project determines the final deliverables.
Data handling
Where your data is processed is a scoping decision, not an implementation detail discovered later. One of these models is chosen and written into the scope.
Data stays on the user's device. No request carrying your content is made.
Suits calculations, conversions and formatting where file sizes allow it.
Data is uploaded for one defined operation and handled under the retention agreed for the project.
Suits work a browser cannot do alone, such as heavier document or batch processing.
Records are stored against your account so history, saved state and sign-in can work.
Used only where saved state or account access is genuinely part of the requirement.
Do not send real credentials or production data in the request form — anonymised samples are enough to scope.
Pricing
There is no price list, because two requests that sound alike can differ by an order of magnitude in work. An estimate is prepared after the review, per project.
One narrow, repeatable task with a single output and few exception cases.
Several connected steps with validation, an exception review and more than one output.
A larger requirement delivered as agreed phases, each usable on its own.
An estimate covers the setup fee and any recurring fee that applies. Submitting a request is free, nothing is billed before you accept a written scope and estimate, and submission does not confirm final pricing.
Prepare
A useful request is a clear description of the work as it happens today. A few sentences on each of these is enough to begin.
Example workflow brief
Questions
That is a common starting point and not a reason to wait. Describe the process as it happens today, including the parts that are inconsistent. The review's job is to turn that into a written summary and a list of the questions that still need answers. If the rules genuinely cannot be pinned down, you will be told that rather than sold a build that cannot work.
Not for the Motifuse-hosted workspace model, where the tool runs on Motifuse infrastructure and your team opens it in a browser after signing in. A dedicated deployment on your own domain or environment is also available, and a handover model exists where you run the tool yourself. Which model applies is decided during scoping and written into the scope — it is not the same for every project.
A delivered tool in the Motifuse workspace sits behind sign-in. You sign in with a password or an emailed sign-in link, sessions are held in a first-party cookie for about 30 days or until you sign out, and every workspace view is scoped to your account. Customer accounts cannot reach administrative areas. Under a dedicated deployment or handover, access control is yours to operate.
Often, yes — when the operation and the file sizes allow it, data can stay on the user's device and no request carrying your content is made. Where server processing is genuinely required, the scope states what is sent, where it is processed, and the retention that applies, before development begins.
Describe the current process, the inputs, the rules that decide the result, the cases needing manual review, and the output you need. Rough volume and any hosting preference help. Anonymised samples help a great deal. Do not include real credentials, identity documents or production data — the request form asks you to confirm you have not.
Per project, after a person has reviewed the request. The estimate reflects the number of workflow stages, the complexity of the rules, the input and output formats, exception handling, integrations, access and storage needs, the deployment model, and any documentation or continued support. An estimate covers a setup fee and any recurring fee. Submitting a request is free, and submission does not confirm final pricing.
Sometimes, and the review will say so. Reconova covers data quality and transformation, and DocForge covers document production. Adopting a maintained product is faster and cheaper than commissioning a build, so it is checked first. An existing product is not modified for a single requester. Where a free public tool already does the job, you will be pointed there instead.
Ownership, source-code access, hosting rights and reuse are set in the written agreement for that specific project. There is no standing package that transfers source code by default, so if source ownership matters to you, raise it during scoping rather than assuming it.
Not automatically. The request form asks whether you are interested in maintenance precisely because it is a scope decision rather than a standard inclusion. Corrections, ongoing maintenance and later phases are included only where the written scope or a subsequent agreement says so.
Small clarifications during a build are expected and normal. A change that alters the approved scope is recorded as a change request, reviewed, and either included without charge or estimated separately before it is implemented — so the scope and the price never drift apart silently.
Start with your workflow
You don't need a software specification. Start with the inputs, repeated steps, rules, exceptions and output you need — the review will tell you whether a private tool, an existing product or a free tool is the right answer.
Example workflow brief
Not sure which path fits?Contact Motifuse