Cloud and SaaS development qualifies as R&D when solving technical challenges that cannot be resolved through routine engineering or existing documentation—going beyond standard product development.
What Qualifies as R&D
Understanding what qualifies as R&D is crucial for maximizing your tax credits. In Cloud & SaaS Software, innovation takes many forms—from breakthrough algorithms to novel system architectures. Here's what the UAE tax authorities recognize as eligible R&D activities:
Novel Architectures: Designing new microservices patterns, developing serverless architectures for unprecedented scale, or creating hybrid cloud orchestration systems
API Scaling & Performance: Experimental work on rate limiting algorithms, novel caching strategies, or database optimisation techniques that push beyond documented best practices
Infrastructure Optimisation: Research into container orchestration improvements, custom load balancing algorithms, or network topology innovations
ML-Driven Features: Developing recommendation systems, predictive analytics, or intelligent automation where outcomes are uncertain
Multi-tenancy Security: Creating new isolation mechanisms, developing novel access control systems, or building zero-trust architectures
Data Pipeline Innovation: Building real-time processing systems with novel consistency guarantees, developing new ETL optimisation methods, or creating custom stream processing algorithms
Observability Systems: Developing new monitoring approaches, creating automated anomaly detection, or building intelligent alerting systems
The Five Core Criteria
Your work must satisfy all five criteria established by the Frascati Manual—the international standard for R&D classification. Here's how these apply to your industry:
Novel (Frascati 2.14)
You're solving problems that aren't answered in Stack Overflow, AWS documentation, or standard textbooks—creating new knowledge about how to achieve specific technical outcomes
Creative (Frascati 2.17)
The work requires original thinking to devise solutions, not just following tutorials or implementing documented patterns
Uncertain (Frascati 2.18)
You don't know if your approach will work, what the performance characteristics will be, or how long implementation will take—distinguishing this from routine development with predictable outcomes
Systematic (Frascati 2.19)
Development follows sprint planning, maintains technical documentation, tracks experimentation, and allocates resources formally
Transferable & Reproducible (Frascati 2.20)
Solutions are documented in technical design documents, runbooks, or internal wikis that allow knowledge sharing across teams
Common Misconceptions
Not every development activity qualifies as R&D. It's important to understand the boundaries. The following activities, while valuable to your business, don't meet the criteria for R&D tax credits:
Feature development following established patterns
Standard CRUD application development
Routine bug fixes and maintenance
Quality control and testing of existing features
Customer-specific customisation as normal business operations
UI/UX improvements without technical innovation
DevOps work using standard tools and practices
The Documentation Challenge
Even when your work clearly qualifies, inadequate documentation can cost you thousands in lost credits. We've seen brilliant innovations go unclaimed simply because teams didn't capture the right evidence. Here's what we've learned from working with hundreds of Cloud & SaaS Software companies:
Common Pain Points
Teams don't distinguish between routine development and genuine R&D
Time tracking doesn't separate experimental work from production coding
Technical decisions aren't documented with alternatives considered
Evidence of uncertainty and iteration gets lost in git commits
Unclear boundaries between product development and research
Best Practices That Work
Label tickets/stories that involve technical uncertainty
Document the 'why couldn't we just Google this?' rationale
Record performance benchmarks and optimization attempts
Maintain architecture decision records (ADRs) showing alternatives
Track time spent on experimental vs. routine development
Keep failure logs showing what didn't work
How We Make It Easy
RDvault was built by engineers who understand the unique challenges of documenting technical work. We automate the tedious parts so you can focus on innovation.
Automatic time-tracking signals from git commits and Jira workflows
Sprint-to-R&D mapping identifying eligible activities
Evidence vault organising technical documentation
Integration with development tools (GitHub, GitLab, Bitbucket, Jira, Linear)
Automated technical narrative generation from engineering artifacts
Does Your Project Qualify?
Ask yourself these five questions. If you answer yes to most of them, you're likely sitting on unclaimed R&D credits:
Are you solving something you couldn't find an answer to through standard research?
Does the work involve technical uncertainty about whether the approach will succeed?
Would a mid-level engineer struggle to implement this following tutorials?
Are you experimenting with multiple approaches before finding a solution?
Does the work require senior engineering expertise and creative problem-solving?
Ready to Claim What You've Earned?
Join forward-thinking Cloud & SaaS Software companies already maximizing their R&D credits with RDvault. Get your personalized eligibility assessment in minutes.