Software development
Define the product and workflow before choosing the implementation.
Discuss your projectA clear brief. Work with a purpose.
Software projects need a shared understanding of users, workflows and constraints. The brief should identify the problem, the systems involved and the conditions for a successful delivery. This page links to work explicitly assigned to software in TROKIT’s portfolio. Specific platforms, integrations and ongoing support are agreed as part of the project scope.
What we can discuss
- Product goals and user requirements
- Interface and workflow design
- Technical scope, integrations and delivery planning
Plan the work around your requirements
Define the brief
Bring your audience, goals, existing materials and the decisions you need to make.
Agree the scope
Discuss deliverables, responsibilities, technical requirements and timing before work begins.
Prepare the handover
Identify the files, content, training or ongoing support your team will need to use the finished work.
Related project work
These projects are connected to software development in TROKIT’s portfolio. Open a case to see its context and deliverables.
Browse the full software development portfolio
Start with the right questions
What makes a useful initial software brief?
Describe who will use the product, the task they need to complete, the systems it must connect to and the constraints on delivery. Existing workflow examples are more useful than a feature list alone.
How are scope, timing and cost agreed?
Share your requirements, current materials and any deadline with TROKIT. The scope, responsibilities and delivery plan need to be agreed for your project before work begins.