Our approach · Martini Software
Understand first.
Then develop.
Good software grows through conversation. We combine an understanding of your production workflows with thoughtful design and an implementation that takes shape step by step.
Starting with the way you work
The right question
comes before
the first feature.
Where does information get lost? Which discussions keep repeating? And where does a change create more work than it should? Many tasks in film and TV production depend on each other. We start by looking at the people, tasks and handovers behind them.
This understanding helps define a sensible project scope. A clearly bounded workflow can be the starting point. What matters is that the solution fits your production and everyone involved understands how it should help in practice.
Close to the workflow.
We look at specific tasks and handovers, grounding requirements in real situations.
Clear about decisions.
We identify goals, priorities and open questions to create a shared basis for the next step.
Open to change.
New findings can change the plan. Together, we assess their effect on scope and effort.
Our process
From the first conversation
to the right application.
Four phases provide direction. The depth of each step depends on the task, the scope and the work already in place.
01 / Understand.
See the workflow.
Define the goal.
We begin with a shared look at your working day. We discuss who is involved in a process, what information is needed and where unnecessary questions or duplicated effort arise. Existing tools, documents and specific situations help us understand these connections.
We distinguish the intended outcome from a possible technical solution. We establish which requirements matter first, what depends on what and which questions remain open. This gives us an initial scope that can be described clearly and assessed together.
What we look at
People, tasks and handovers
Existing data and applications
Goals, priorities and constraints
What comes out of it
A shared starting point: the problem, the intended benefit and a clearly defined first step.
02 / Design.
Give requirements
a clear shape.
Before developing features, we give the workflow a structure. Which information belongs together? Which views are needed? And how will users know what to do next? We turn requirements into understandable paths through the application.
Depending on the task, sketches or clickable prototypes make the solution easy to discuss early on. Using practical work scenarios, we review whether labels are clear, important information stands out and feedback provides direction. We also consider permissions, mobile use and different processing states where they are relevant to the project.
What we look at
Information structure and user journeys
Interfaces and understandable states
Roles, access and use scenarios
What comes out of it
An agreed concept that makes the planned workflows and essential features tangible.
03 / Build.
Step by step.
With the whole picture in view.
Development follows the agreed scope and manageable work packages, allowing us to discuss progress at useful intervals. We always consider individual features in the context of the workflow they serve, including the data and systems involved.
Testing covers the intended path as well as questions and exceptions: missing information, different permissions or interrupted transfers. Feedback from joint reviews informs the next steps. New requests are assessed in terms of their value and their effect on effort and timing.
What we look at
Manageable development stages
Testing of features and workflows
Review of feedback and changes
What comes out of it
A tested version for the agreed use, with traceable decisions and clearly identified open points.
04 / Develop further.
Put it into practice.
Build on experience.
For the introduction, we establish how the application will become part of your working practices. This may include migrating existing data, an introduction for users and a staged rollout. Prerequisites and responsibilities are agreed before deployment.
Actual use then shows which features work well and where further needs arise. This can lead to targeted improvements and additional use cases. Hosting, maintenance, support and ongoing development are agreed for each project. Responsibilities and the handling of changes remain part of our collaboration after launch.
What we look at
Introduction and data migration where needed
Agreements on operation and support
Improvements informed by actual use
What comes out of it
A usable foundation and an agreed framework for operation and further development.
Working as partners
Good decisions
are made together.
You know your production. We bring a perspective on structure, design and implementation. Regular conversation connects the two.
Your knowledge makes the difference.
Specific workflows, typical difficulties and feedback from future users help us ask the right questions. A complete requirements specification does not have to be the starting point. Together, we gather what really matters for the task.
Progress makes it tangible.
A design or a working feature is easier to discuss than an abstract description. We agree suitable review points, collect feedback and record decisions, so the basis for the next step remains clear.
Give changes a framework.
Requirements can evolve. We discuss which changes are useful, what they affect and how they should be prioritised. Scope, responsibilities and next steps are agreed together before new requests become part of the project.
For our first conversation
A specific workflow
is a good place to start.
Describe a situation that currently takes more effort than it should: who is involved, what information is needed and what should become easier? Existing documents or a brief description of your tools can help.
Together, we establish which questions need answers next. From there, we can define a first step that fits your task and the conditions already in place.
The next step starts with a conversation.
What should your software
make possible?
Tell us about your idea, your process or your next challenge.