MARMATIONDiscuss a project
MARMATION

Start with what matters.Choose the software around it.

Discuss a project

AI Product Strategy & Development

AI Product Strategy & DevelopmentProduct judgment. Working software.

The next generation
of software is intelligent.
We build it.

Build a product around your expertise. Put company knowledge to work. Connect the tools your team already uses.

Product direction on its own, or design and delivery. Build on the software you have, or develop what the business needs.

Explore the outcome menu Get product direction
How the parts fit togetherProduct design, AI and existing systems need to work together. Clear access rules, testing and human review turn a promising feature into useful software.
Product thinking. Systems engineering.
01 / Twelve ways to move the business forward

The business
outcome menu.

Pick a problem worth solving. Open a solution to see what could change, how we would measure it and what it needs to work.

Examples of possible work. Scope and measures are agreed for your business.

Products your customers use.

Give people a better way to use your expertise, choose an option or get something done.

A product built around your expertise

Measure to agreeTask completion · repeat useYour advice is valuable. Delivering it always needs someone in the room.
What could change
Shape a customer product around a repeatable part of your service: guided analysis, recommendations or a review workspace. Design the experience, test demand and build the useful first release.
How we would judge it
Customers can complete the task, understand the result and find a reason to return. Test willingness to pay where it is a paid product.
What it depends on
Your subject expertise, access to prospective users, rights to the source material and clear limits on the advice the product may provide.
Explore this solution

A client portal that moves work forward

Measure to agreeTime to approvalCustomers chase updates. Your team keeps answering the same emails.
What could change
Give customers one place to submit information, review work, approve a decision and see what happens next. Extend an existing customer platform or develop a focused application around the service.
How we would judge it
Completed requests, time to approval and how often customers need staff help. Check accessibility and correct customer access alongside adoption.
What it depends on
The systems holding customer records, identity and access rules, the service process and who owns the response after a customer acts.
Explore this solution

An intelligent feature in your existing product

Measure to agreeSuccessful feature useThere is a useful AI idea. It still needs to fit the product people already use.
What could change
Add a focused capability such as document review, supported search or a draft recommendation. Connect it to the existing interface, account permissions and saved work.
How we would judge it
Successful task completion, repeat use, correction effort and cost per useful result. Compare the experience with the current way of working.
What it depends on
Access to the product, representative user tasks, appropriate information and agreed quality, response-time and operating-cost limits.
Explore this solution

Help customers choose the right option

Measure to agreeQualified conversionsYour catalogue is clear to specialists. Customers still need help choosing.
What could change
Build a guided selection or advisory experience that explains relevant options, checks requirements and hands a qualified request to the right person or system.
How we would judge it
Correct selections, completed enquiries and qualified conversions. Keep unsuitable recommendations and customer confusion visible.
What it depends on
Current product information, compatibility or eligibility rules and a route to a person when the information cannot support a recommendation.
Explore this solution

Knowledge people can put to work.

Make the information you already have easier to find, check and use.

Answers from your company knowledge

Measure to agreeTime to a supported answerThe answer exists. Finding the right version takes three people.
What could change
Connect approved policies, project records and service information to a useful search or assistant experience. Start with existing platform capabilities where they fit; add retrieval and a tailored interface where needed.
How we would judge it
Time to a correct, supported answer, source freshness and how often staff must step in. Test restricted and unanswered questions too.
What it depends on
Identifiable source owners, permission rules, representative questions and agreement about where company information may be processed.
Explore this solution

A better way to review documents

Measure to agreeReview time · missed issuesPeople read the same files, compare the same details and still miss changes.
What could change
Create a workspace that extracts the relevant details, compares versions and puts evidence beside a suggested finding. Keep the reviewer in control of the final decision.
How we would judge it
Review time, missed issues, incorrect findings and the effort needed to correct them. Agree what must always go to a specialist.
What it depends on
Representative documents, a shared definition of a correct finding, rights to process the files and the qualifications needed for the final review.
Explore this solution

Research and reporting without the repeat preparation

Measure to agreePreparation time · correctionsEvery report starts with another round of collecting and checking information.
What could change
Connect approved sources, prepare repeatable analysis and produce a reviewable report with linked evidence. Keep calculations and agreed business definitions explicit.
How we would judge it
Preparation time, factual corrections, data freshness and whether the report supports the decision it was made for.
What it depends on
Reliable source access, agreed measures and calculation rules, report ownership and a reviewer who can judge the conclusions.
Explore this solution

Proposals grounded in what your business can deliver

Measure to agreeProposal preparation timeThe team keeps rebuilding answers from old proposals and scattered notes.
What could change
Bring approved capabilities, project material and reusable answers into a proposal workspace. Draft against the request, link the supporting material and flag commitments that need approval.
How we would judge it
Preparation time, unsupported claims, review effort and proposal usefulness. Treat win rate as a broader commercial measure, not proof that drafting alone caused a sale.
What it depends on
Approved source material, confidentiality rules, current commercial terms and someone accountable for the final offer.
Explore this solution

Work that gets all the way through.

Connect the requests, records and decisions your team currently has to chase.

From customer request to a checked quotation

Measure to agreeQuote turnaroundA straightforward quote still waits for details, prices and someone to approve it.
What could change
Capture the request, find the relevant product and pricing information, prepare a quotation and route exceptions for approval. Use the CRM, field-service or finance platform that should hold the record.
How we would judge it
Time to an accurate quote, corrections, approval delays and margin exceptions. Follow quote acceptance without promising a conversion uplift.
What it depends on
Current prices and product data, approval rules, supported platform access and an owner for unusual requests.
Explore this solution

Customer onboarding with fewer loose ends

Measure to agreeTime to readinessThe sale is complete. Delivery is still waiting for the right information.
What could change
Connect forms, documents, customer records and team handoffs. Show what is missing, who needs to act and when the customer is ready for the next stage.
How we would judge it
Time to readiness, repeated information requests and stalled handoffs. Check that required consent, approval and customer access remain intact.
What it depends on
An agreed onboarding process, the relevant CRM or service system, ownership at each handoff and a clear route for exceptions.
Explore this solution

Documents checked and ready for the next step

Measure to agreeCost per correctly completed itemIncoming forms and attachments become another queue of manual data entry.
What could change
Read incoming documents, check required fields and prepare records in the system of record. Send unclear items to a review queue and make retries safe.
How we would judge it
Cost per correctly completed item, exception rate and duplicate prevention. Reading a document is only part of completing the work.
What it depends on
Representative files, validation rules, supported write access and a person or team responsible for unresolved items.
Explore this solution

Service requests that reach the right resolution

Measure to agreeCorrect resolution · time to helpStaff spend time sorting requests before they can start helping.
What could change
Classify incoming requests, retrieve approved answers, prepare responses and route work into the service platform. Use native support features where suitable, with human handoff for sensitive or uncertain cases.
How we would judge it
Correct resolution, time to help, repeat contacts and customer experience. Review the quality of closed requests as well as queue length.
What it depends on
A maintained knowledge base, routing and escalation rules, access to the service system and clear ownership after handoff.
Explore this solution

Several of these situations may belong in one product or workflow. We scope the complete job, including the people and systems around it.

Talk through one problem
See how a product, a knowledge tool and a workflow differ.
01 / Three places to make a difference

Where could better software make a difference?

A better experience for customers. Answers your team can find. Work that moves without another spreadsheet. Start with the change that matters.

01 / For your customers

AI products

Build something people choose to use.

Turn your expertise into a client portal or intelligent feature. Help customers compare options, review a suggestion and act.

  1. Your customer describes the needA service package to compare
  2. The product helps them chooseOptions grounded in your expertise
  3. Your customer confirmsA saved choice your team can act on
An illustrative guided selection, with the customer making the final choice.

Worth measuringCan customers finish the task, and do they come back?

A product built around your expertiseAn intelligent feature in your existing product
Explore AI products
02 / For your team

Company knowledge

Put the right answer within reach.

Make policies, project files and service knowledge easier to use. Give your team supported answers from current sources they are allowed to see.

“Which policy applies here?”

Find
Current, permitted sources
Explain
An answer linked to the evidence
Know the limit
Say when the answer is missing
An example question, answered from approved information.

Worth measuringCan people find a supported answer without asking around?

Answers from your company knowledgeA better way to review documents
Explore company knowledge
03 / For the business

Business workflows

Make the whole process work.

Connect a service request from sales to delivery, with the information, approvals and next action in the tools you already use.

  1. Request received
  2. Person or rule approves
  3. Next team can act

When something stops: show what is waiting and who can resolve it.

An example handoff, with a route for unfinished work.

Worth measuringDoes work finish with fewer handoffs and less rework?

From customer request to a checked quotationCustomer onboarding with fewer loose ends
Explore business workflows

These are examples of possible work, not client case studies. The first step is to establish what would be useful in your business.

Several of these tasks may belong in one product or workflow.

Explore the full solution menu

The right software.
For your business.

Build on what already works. We bring product strategy and implementation together across business platforms, automation tools and custom applications.

The choice follows your requirements, existing investment, running costs and ability to operate the result.

Microsoft / Dynamics 365SalesforceServiceTitanHubSpotGoHighLeveln8n

Configure

The platform already has the capability.

Extend

The platform fits. One important piece is missing.

Connect

Useful systems leave work stuck between them.

Build

The product or requirement needs software of its own.

The same business goal can need different implementations. Check platform editions, supported APIs, access, licensing and data terms before committing. Include maintenance and future changes in the comparison.

How we choose the approach
02 / Try it for yourself

Good ideas deserve
a working test.

A product needs to handle mistakes. A knowledge tool needs to respect access. A workflow needs to recover when a connection fails. Test those decisions before expanding the build.

The Lab includes one working order-review example with sample data and fixed rules, alongside proposed product and knowledge designs. Use it to inspect how a small part of a system behaves.

Explore the Lab
Inspect the working order-review example
Document operationsRecorded steps from the browser example

Change the order. Check it again.

Example order / PO-2001 / sample data

  1. 01
    Change quantity: 12 → 13Approval cleared
  2. 02
    Try saving before approving the changeNot saved · fresh approval needed
  3. 03
    Approve, save, then save againOne order saved · no duplicate

Changing the quantity means someone must approve the new version. Saving it twice still creates just one order.

This example uses sample orders and fixed rules in your browser. No AI model or customer system is connected.
Try the order review
03 / Before you invest

Five questions worth answering first.

Before choosing a model or a supplier, agree what should improve, how you will check it and who will look after the result.

You may already own software that can do the job. Compare buying, adding to an existing tool, connecting systems and building something new.

Compare the four routes How we move from decision to delivery
Value

Which change earns the investment?

Choose one task and agree what better would look like: less rework, a faster review or a more useful customer experience. Measure today’s process first, including the cost of changing it and the reasons to stop.

What to agree

A picture of today’s process, a measure of success and one useful first release.

Control

What is the system allowed to do?

Decide what the software may see, suggest and change. Follow company information through the connected tools and AI service. Agree who can access it, how long it is kept and which actions need a person’s approval.

What to agree

A clear map of where information goes, who may use it and what needs approval.

Quality

How will we know it works?

Choose real kinds of work to test, including missing information and mistakes that would be costly. Use the same examples to check each release. Agree when the software should stop and ask a person.

What to agree

Example tasks, agreed standards and a clear way to involve the right person.

Economics

What will a useful outcome cost?

Include the AI service, hosting, licences, connections, human review and support. Look at the cost of finishing a useful task as well as the monthly bill. A cheap answer is not good value if someone has to redo the work.

What to agree

An estimate based on expected use, review time and support, rather than just the price of the AI model.

Ownership

What happens if it works?

Decide who will run the software, who will improve it and what the team will do with the time it saves. Agree the access, documentation and support they need to take over confidently.

What to agree

A named owner, practical operating instructions and a plan to help people use it.

04 / Go deeper into the architecture

How the pieces work together.

Explore the decisions behind a product, company search tool or internal workflow: who can use it, what it can access and what happens when something goes wrong.

Systems Atlas3 types of system · 18 design decisions

Systems Atlas

Change the business context. Open a layer. Inspect the decision, what can fail, and the evidence worth asking for.

Intelligence inside a product.

Follow a customer’s task from the first request to a checked result. See where privacy, corrections and approval belong.

Example system designLocal / not connected
  2. Read this decision
  • The customer’s task to Customer privacy: Check the user and customer account.
  • Customer privacy to Relevant information: Limit access to permitted records.
  • Relevant information to The AI suggestion: Provide relevant permitted information.
  • Customer privacy to The AI suggestion: Limit what the AI may do.
  • The AI suggestion to Permitted actions: Validate the proposal.
  • Permitted actions to Check each release: Observe the task result.
  • Check each release to The customer’s task: Improve the product task.
DependencyEvidenceFeedback / recoveryChoose a step to learn more

Customer privacy

AUTH
The decision to make
Check which customer account and user are making the request before looking up information or taking action. Carry those access rules through searches, stored answers and connected tools.
What could go wrong
One customer sees another customer’s records through a search, a stored answer or a connected tool.
What to ask the team to show
  • Tests that try to cross between customer accounts.
  • A list of what each user role may view or change.
Return to the diagram

A model may propose an action. The product must decide whether it is allowed.

Example system design.
Not a customer deployment.
05 / From the Marmation Review

The decision behind the technology.

Browse all perspectives
What actually
needs to change?
Buy
An existing product meets the important requirements.
Extend
A platform fits; a focused addition closes the gap.
Integrate
The value comes from making existing systems work together.
Build
A distinctive product or workflow warrants a system of its own.

Four options to evaluate. Requirements decide the route.

Decisions / 5 min

Build, buy, extend or integrate? The AI decision that comes before the technology.

Read when: The roadmap needs a build-or-buy decision.

Read the article

Bring us the
difficult part.

A product idea, a broken workflow, scattered company knowledge or an integration others keep working around. Tell us what needs to change and what has already been tried.

Discuss a project