Products & platforms
New functionality, system architecture and the technical work behind a product roadmap.
Software.
Support for software businesses and development teams evaluating technical work, research costs and the operating demands of growth.
Industry context
Get close to the development work.
A product roadmap tells only part of the story. The technical questions, approaches considered and decisions recorded during development help explain what your team actually did.
We work with the people responsible for development and finance to understand the projects, the costs and the business context before recommending a scope.
Internal systems
Software developed for use within a business, including the purpose and users of the system.
Commercial growth
Go-to-market planning, sales processes and operating systems for a growing software business.
Where we
can help.
We define the engagement around the questions you need answered and the information available.
Assess development activities
Review the technical objectives, uncertainty and evaluation of alternatives within particular projects. Routine changes and development work need to be considered on their own facts.
Review the delivery arrangements
Understand employee and contractor involvement, development locations and relevant agreements before assessing the work and costs.
Support the business around the product
Help work through market priorities, sales and marketing strategy and the practical systems needed to support growth.
A closer look
The repository is part of the evidence.
Tickets, design documents, test results and version history can help explain the development work. They need context from the people involved. We consider how the available records relate to the technical questions and the costs being reviewed.
Preparing to talk
What to bring to
the first discussion.
Bring a description of the product, a few recent development projects and an overview of where the team works. Identify the tools used to record development and the agreements covering outside contributors.
You do not need to assemble a full study before speaking with us. The initial conversation helps establish whether there is a useful scope for Royse and what the next step would involve.
Questions
to work through.
These points help frame the discussion. Conclusions depend on the engagement facts.
Is all software development eligible for R&D credits?
No. Eligibility depends on the activities, applicable requirements and exclusions. Software developed for internal use can raise additional questions, which need to be considered as part of the review.
Do you need access to our entire source-code repository?
We agree on the information needed and how it will be shared before collection. The first discussion should establish the projects and available records rather than defaulting to broad system access.