Different industries. Recurring systems problems.
Industry context changes the vocabulary, data and risk. It does not eliminate the engineering fundamentals. Marmation organizes work around buyer problems and uses industry examples to make them easier to recognize.
Which operating boundary makes your problem different?
The industry name provides context. The useful brief identifies a product or process, the decision it must support and the conditions it must preserve. Start there before choosing a model or commissioning software.
Illustrative operating contexts, derived from the V5 manuscripts. These are use cases and constraints, not evidence of completed sector projects or a qualified sector practice.
Recurring problems. Different consequences.
Read across a row to connect the business job to its engineering boundary. Each example needs its own data, sponsor and acceptance evidence.
B2B software
Illustrative contextEmbed a useful capability in an existing customer workflow.
Tenant, role and product stateCan the feature preserve the customer's existing permissions?
Industrial distribution
Illustrative contextReconcile a quote or order with the system of record.
Product, unit, price and approved write-backWhich differences must a person resolve before an order exists?
Commercial field services
Illustrative contextConnect a request, dispatch, field evidence and billing.
Work-order state across handoffsWhat happens when the technician's record arrives late?
Professional services
Illustrative contextFind and use the right knowledge within a client workstream.
Source authority and professional reviewWho can access this source, and who approves the resulting work?
Technology-enabled services
Illustrative contextExpress repeatable operating knowledge in a useful interface.
Repeatable logic and retained human judgmentDoes software improve a service step customers actually value?
Telecommunications
Illustrative contextSupport one customer or employee task across existing systems.
Account authority and reconciled service stateWhich system can authorize the action, and which confirms its result?
An industry page cannot qualify a project.
A formal practice needs substantiated project work and personnel. Before accepting work, establish whether the proposed team and approvals fit the actual operating conditions, especially in regulated or safety-critical environments.
- A sponsor with authority over a bounded business job.
- Access to representative data and the relevant system owners.
- Explicit security, legal, procurement and specialist requirements.
- A qualified delivery team and a practical acceptance boundary.
Bring the handoff that keeps breaking.
A customer action, a document or an operational exception is a more useful starting point than a sector label.
- Useful evidence for the first conversation
- Bring an example of the current work, its system boundaries and the person accountable for the next decision.
The argument for context before claims
For CTO, CIO, CPO, COO
The situation behind the request
A distributor reconciles incoming orders; a software company embeds AI in customer workflows; an equipment service business coordinates work across locations. Each needs identity, data integrity, integrations, usable interfaces and accountable decisions, although the details differ.
Where the obvious solution falls short
A consulting firm claiming deep specialization in ten sectors without verifiable case work is difficult to trust. We will not manufacture industry success stories simply to fill pages.
How we would approach the work
Industry pages describe realistic application patterns and sector-specific constraints, clearly labeled as use cases, not claimed client outcomes. A formal industry practice should be added only when project work and personnel substantiate it.
What the engagement may include
- B2B software and technology platforms.
- Industrial and wholesale distribution.
- Commercial services and field operations.
- Professional services and selected enterprise environments.
The choices worth making explicitly
Heavily regulated or safety-critical work may require credentials, security controls, specialist expertise or procurement eligibility beyond an initial project. We qualify such assignments before accepting them.
What we would test before calling it ready
The relevant test is not whether a sector is fashionable; it is whether an engagement has a sponsor, a bounded business job, clear data and delivery constraints, and a qualified team.
A sensible first step
Start with your process or product requirement; the industry label is useful context, not a substitute for a project brief.