Skip to content
BigTree108

Research and audit services

Research and audits before and during a software project: market and competitor research, discovery and technical specification, R&D and proof of concept, code and technical audits and website audits, each ending in a written report you can act on, with dedicated analysts and engineers for your team or a study delivered end to end.

Research and audits we carry out

Each page covers what the work includes, what you receive at the end and the questions clients ask first.

Covered elsewhere on the site

How every study and audit runs

  • The question first

    Each study starts from the decision it has to inform, written down and agreed with you before any research or review begins.

  • A fixed scope and date

    The sources, the methods, what is in scope and the date of the report are agreed in writing, so the work ends when the plan says it will.

  • Evidence behind every finding

    Each finding links to the source, the interview, the line of code or the measurement it comes from, so you can check it yourself.

  • Findings ranked by impact

    Results are ordered by what they change for your decision, with the effort each recommendation needs, rather than listed in the order they were found.

  • A report you own

    The report, the raw data and the working files are delivered into your accounts, written so that your own team can act on them.

  • The same team can build

    Researchers, analysts and the engineers who build software work in one company, so a finding becomes a plan and then a release without a hand-off between vendors.

Choosing where to start

Before a product or a new market, market and competitor research tells you whether there is demand and who already meets it. Before a build, discovery turns the idea into a specification, a prototype and an estimate. When the question is whether something can be built at all, an R&D project or a proof of concept answers it on a small scale first.

For software that already exists, a code and technical audit shows the state of the code, the architecture and the infrastructure, and a website audit shows what holds a site back in search, speed, accessibility and security. Each one ends in a written report, and the work it recommends can be done by your own team or by ours.

Specified, built and audited by the same team

We specified and built the platform we run our own company on: hiring, onboarding, contracts, time tracking, leave, compensation and invoicing, on .NET, Angular and Azure. Every take-over of a system another team wrote starts the way a code audit does, with a read-only review and a written list of risks. Read the case study.

Questions about research and audits

Can research or an audit be bought through a tender?

Yes. We are open to tenders, including public procurement on Prozorro. In DK 021:2015, the Ukrainian version of the EU’s CPV classifier, research and development comes under 73000000-2 and market research under 79310000-0.

Do we have to hire you for the work the report recommends?

No. The report is yours, written so that your own team can act on it. If you want us to do the work, the people who found the problems can fix them, under a separate plan and estimate.

How are research and audits contracted and billed?

As a fixed-scope piece of work with an agreed report date, or as ongoing hours for research that continues. Either way there is one agreement with BIG TREE 108 LLC and one invoice a month, with time logged in our own portal.

Who owns the reports and the data?

You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.

Need an answer before you decide?

Tell us the decision you are facing and what you already know. You get an answer within one business day: a proposed scope for the study or audit and the date the report would be ready.