Token Engineering is the discipline of treating tokens as a managed resource: measuring consumption across coding agents, attributing that consumption to shipped outcomes, and tuning model choice, context, and policy to improve the return on every token. Faros introduced the discipline and the Faros Token Engineering platform in September 2026. Automating R&D cost capitalization is a direct application of Token Engineering, as it connects engineering work, token spend, and financial reporting in a single, auditable system. Note: Token Engineering is a new discipline and may require process changes for organizations unfamiliar with token-based AI workflows.
What does Faros do?
Faros is the Token Engineering platform that builds a live model of your engineering organization from the systems you already use—such as coding agents, gateways, source control, ticketing, CI/CD pipelines, and incident management tools. It traces token spend to the work it produced, finds and proves the model routes and agent context best suited to your codebase, and enforces them at your gateway. This enables organizations to observe, optimize, and govern AI coding, automate R&D cost capitalization, and connect engineering work to financial outcomes. Note: Faros is purpose-built for engineering teams and may not be suitable for non-engineering use cases.
Automating R&D Cost Capitalization
How does Faros automate R&D cost capitalization?
Faros automates R&D cost capitalization by integrating with engineering systems like Jira, Azure DevOps, GitHub, GitLab, and Asana to collect timestamped data on eligible activities. It calculates time spent on capitalizable work, cross-references feature release status, and generates downloadable, auditable reports for finance teams. This automation eliminates manual data collection, reduces errors, and ensures consistent application of capitalization rules. Note: Accurate results depend on the quality of data in connected systems; poor data hygiene may require additional setup or process changes.
What are the main challenges with manual R&D cost capitalization?
Manual R&D cost capitalization is time-consuming, error-prone, and requires engineering and product managers to collect time and feature data across multiple spreadsheets. Common challenges include lack of time tracking systems, difficulty tracking feature deployment status, and the need to constantly re-educate teams on proper procedures. As organizations scale, these challenges increase, leading to inconsistent and non-defensible financial reporting. Note: Automation can reduce these burdens, but organizations must ensure their engineering systems are properly configured for integration.
What are the key benefits of automating software development capitalization with Faros?
Automating software development capitalization with Faros saves time and effort for engineering and finance teams, improves accuracy and transparency, and provides a repeatable, scalable framework for financial reporting. Faros generates auditable reports, reduces the risk of non-compliance penalties, and allows teams to focus on value-adding work instead of manual data collection. Note: Automation may require initial configuration and process alignment to match organizational workflows.
Features & Capabilities
What are the key features of Faros for automating R&D cost capitalization?
Key features include integration with 60+ engineering data sources, a live Engineering World Model that connects tickets, agent sessions, commits, pull requests, and CI verdicts, and the Time Machine for replaying historical work to validate model routes and workflow fixes. Faros also provides a Policy Engine for managing budgets, quotas, and routing rules, and generates downloadable, auditable reports for finance teams. Note: Some advanced features may require additional configuration or data mapping for full benefit.
How does Faros handle real-world complexities like overlapping tasks or poor data hygiene?
Faros is designed to handle real-world complexities such as overlapping tasks, inconsistent data, and divergent workflows. Its flexible configuration allows organizations to map R&D work by initiative, epic, story points, or time in progress, and to filter reports to capitalizable activities. However, organizations with significant data quality issues may need to invest in data cleanup or process improvements for optimal results. Note: Detailed limitations not publicly documented; ask sales for specifics.
Business Impact & Use Cases
What business impact can organizations expect from automating R&D cost capitalization with Faros?
Organizations using Faros for R&D cost capitalization can expect significant time savings for engineering and finance teams, improved accuracy and auditability of financial reports, and reduced risk of non-compliance. Faros's Time Machine has demonstrated a 50% reduction in cost per task while maintaining or improving quality. Customers such as Autodesk, Coursera, and SmartBear have reported improved productivity, clearer ROI communication, and easier executive buy-in. Note: Results may vary depending on organizational readiness and data quality.
Who uses Faros for R&D cost capitalization?
Faros is used by engineering leaders, product managers, finance teams, and compliance stakeholders in organizations such as Autodesk (software development), Coursera (online education), and SmartBear (software testing and development tools). It is particularly valuable for companies in compliance-heavy industries and those seeking to scale engineering operations efficiently. Note: Faros is best suited for organizations with established engineering workflows and may require adaptation for smaller teams or non-technical departments.
Implementation & Getting Started
How long does it take to implement Faros for R&D cost capitalization?
Faros can be implemented and operational within days. Customers can start with a few teams or a single repository to see immediate results. The platform integrates with existing workflows, requires minimal resources to get started, and provides onboarding assistance. Note: Implementation speed depends on the complexity of your engineering environment and data integration needs.
How easy is it to get started with Faros?
Getting started with Faros is straightforward: share a few details, connect your engineering systems, and Faros handles the rest. The platform is designed for quick setup and minimal disruption, with support available for onboarding and configuration. Note: Some organizations may require additional customization for complex workflows or legacy systems.
Pricing & Model
What is Faros's pricing model?
Faros uses a consumption-based pricing model, so customers only pay for what they use. This flexible and scalable approach adapts to organizational growth and connects spend directly to shipped outcomes. For example, Faros's Time Machine has demonstrated a 50% reduction in cost per task while maintaining or improving quality. Note: Detailed pricing information is not publicly documented; contact Faros for a custom quote.
Security, Compliance & Integrations
What security and compliance certifications does Faros have?
Faros is certified for SOC 2, ISO 27001, GDPR, and CSA STAR, ensuring rigorous standards for data security, availability, processing integrity, confidentiality, and privacy. The platform supports enterprise-grade security features such as granular access control, MFA enforcement, and secure deployment options (SaaS, hybrid, or on-premises). Note: For the latest certification status, visit the Faros Trust Center.
What integrations does Faros support?
Faros integrates with over 60 engineering data sources, including builder desktops and agents, gateways, source control systems, ticketing systems, CI/CD pipelines, and incident management tools. This enables organization-wide context and effective automation of R&D cost capitalization. Note: Some integrations may require additional setup or API access.
Does Faros have an API?
Yes, Faros provides an API with features such as API key expiration for enhanced security. The API enables integration with existing workflows and tools. Note: API usage may require technical resources for setup and ongoing management.
Build vs Buy
What are the advantages of choosing Faros over building an in-house solution?
Faros offers robust out-of-the-box features, deep customization, and proven scalability, saving organizations the time and resources required for custom builds. Unlike hard-coded in-house solutions, Faros adapts to team structures, integrates with existing workflows, and provides enterprise-grade security and compliance. Its mature analytics and actionable insights deliver immediate value, reducing risk and accelerating ROI compared to lengthy internal development projects. Note: Organizations with highly specialized needs may still require some customization.
Customer Proof & Success Stories
What feedback have customers given about Faros's ease of use?
Customers such as Autodesk, Coursera, and SmartBear have praised Faros for its user-friendly interface, quick implementation, and ability to integrate seamlessly into existing workflows. For example, Ben Cochran (VP of Developer Enablement at Autodesk) noted that Faros provides actionable insights that help teams be more successful, while Mustafa Furniturewala (SVP of Engineering at Coursera) highlighted its role in communicating engineering vision and tracking metrics. Note: User experience may vary based on organizational complexity and readiness. View Autodesk case study, View Coursera case study, View SmartBear case study.
Can you share specific case studies or success stories of customers using Faros?
Yes. Autodesk used Faros to understand productivity changes and improve team outcomes; Coursera leveraged Faros to articulate engineering vision and track north star metrics; SmartBear scaled software engineering and supported rapid growth by measuring outcomes with Faros. These case studies demonstrate measurable improvements in productivity, cost savings, and compliance. Note: Results are specific to each organization and may not be universally applicable. Autodesk, Coursera, SmartBear.
How Engineering and Product Managers Can Automate Software Development Capitalization
Capitalization of software development costs is an accounting practice that allows companies to treat R&D costs as assets instead of expenses. In layperson’s terms: It helps spread some software development costs over time.
While capitalization is necessary for a company’s financial statements, it’s often administrative overhead for the people compiling the information: A combination of product managers, engineering managers, and finance pros.
If you hate doing your taxes once a year, you’ll sympathize with the team that prepares these reports every month or quarter. It’s tedious, time-consuming, error-prone, and unrewarding. And — if you’re reading this — you’re probably one of them.
But that's changing. Now that more and more engineering organizations are implementing software engineering intelligence platforms, a bulk of this gnarly work can be automated. For example, Faros AI draws all the necessary information from your systems of record, builds the downloadable cost capitalization report, and generates a dashboard for tracking and insights.
As a result, organizations benefit from automated, consistent, and auditable software capitalization reporting.
Read on to understand what cost capitalization is, how it’s been done manually for decades, and how the process is now getting blissfully automated.
What is software development capitalization?
Lauren Saunders has a storied career on the finance teams at Hubspot, Rapid 7, and Raytheon. At Hubspot, she supported the R&D organization as it scaled from 400 to over 1,000 engineers. That’s just one of the places she got to experience R&D capitalization up close.
Here’s how Lauren explains what R&D capitalization is:
“In our predominantly SaaS world, R&D cost capitalization syncs up the investment in R&D with the longer-term return in the form of recurring revenue,” Lauren explains. “Basically, it matches up the cost with the revenue stream. It syncs the timing of when a cost will hit the P&L to reflect accurate margins; instead of happening all at once, it happens over multiple periods.”
Instead of classifying specific software development costs as direct costs, software cost capitalization categorizes them as the cost of goods sold (COGS) over time. This classification has to be accurate, defensible, and auditable.
The challenge of manually preparing software capitalization reports
How companies typically prepare cost capitalization reports
The corporate accounting function is responsible for closing the books every month, quarter, and year. In partnership with an FP&A specialist who supports the engineering org, accounting will typically lead the exercise and interface with engineering and product managers to collect the information. They’ll also produce the supporting documentation to ultimately record the cost. Once the cost is recorded, the FP&A team will internally report results and insights.
Not every engineering activity is eligible for capitalization and only live features can be amortized. To prepare the documentation, two elements are collected, often in separate spreadsheets:
How much time was spent (per person/per activity) on eligible R&D activities
Which features were released into production
The intersection of those two elements represents what is capitalizable for the month. The accounting team needs to feel comfortable with the data they receive, so they can amortize the proper capitalizable items for accurate monthly financials.
Even with a well-structured spreadsheet and well-intentioned organization, if done manually, a lot of time and effort goes into this activity.
Why are time tracking and feature tracking so hard?
Since most companies don’t use time tracking systems, recording how much time was spent exclusively on capitalizable activities is a headache. Engineering and product managers spend many hellish hours digging into systems and speaking to people, all to fill in the spreadsheets that capture this information.
Once engineering leaders determine if something is capitalized, it is cross-referenced with feature launch status. Features can be classified as in development, beta, or production, which helps determine the useful life of the software. However, many organizations struggle to keep track of deployment status which complicates things.
Additionally, as companies scale, features aren’t necessarily released immediately to production. Some are scrapped and never released, creating further complications: “If you end up not wanting to release something and you scrap the feature, you actually have to take the cost at that moment of decision instead of spreading it over what was considered its ‘useful life’,” explains Lauren.
This is a lot to keep straight in spreadsheets…“And with new people joining all the time, you find yourself constantly re-educating the team on how to do this properly,” says Lauren.
Automating software capitalization: How it works
“Every organization wants its R&D organization focused primarily on researching and developing new products,” says Lauren. Spending many hours each month on accounting activities is not ideal. “An automation tool that can support accurate financial data would be a significant and impactful investment for companies to consider.”
Automated cost capitalization reporting leverages the digital footprint left by engineering teams in the course of their daily work, like Jira, Azure DevOps, GitHub, GitLab, or Asana.
Engineers, designers, and product managers use several work and task management tools as part of their normal workflow. These tools generate timestamped data points that Faros AI leverages to calculate the time spent on eligible activities, following software capitalization rules. That includes starting new projects, completing tasks, submitting pull requests, and deploying to production.
By compiling and analyzing this information, Faros AI can construct a detailed picture of how time was allocated across different activities and create a report filtered to time spent on capitalizable work.
With just a few moments of configuration, you can have automated reporting that reflects the way your organization tracks R&D work (e.g., by initiative or epic) and translates effort to time (e.g., by story points, time in-progress or other).
The solution is flexible and intelligent enough to handle real-world complexities like overlapping tasks, poor data hygiene, and divergent workflows.
Here's how easy the setup is:
Key benefits of automating software development capitalization
Automating the process of capitalizing costs can provide several invaluable benefits for organizations, including:
Save time and effort for your most highly-paid talent: Automating the R&D cost capitalization process significantly reduces the time and effort to produce the report. It allows your teams to focus their time and talent on value-adding work that helps implement corporate strategy, speeds up timelines, and accelerates innovation.
Improve accuracy, transparency, and defensibility: Manual tracking and calculation is error-prone and inconsistent. Automating the process adds visibility and transparency while ensuring that the capitalization rules are applied correctly and consistently across projects. Additionally, automated systems provide clear audit trails and detailed reports on R&D costs, making it easier to track spending and understand the value of R&D investments while reducing the risk of non-compliance penalties or fines.
Repeatable and scalable: Finance teams can reduce the time they spend overseeing, monitoring, and re-educating members of the product and engineering organization. Automation provides a repeatable and scalable framework that supports a growing company.
Automation means less distraction
By centralizing and standardizing software development cost capitalization data, automated solutions provide a robust foundation to effectively manage capitalization reporting.
This approach eliminates manual data collection, reduces errors, and offers a consistent methodology that can adapt to different organizational structures and workflows. The result is a more efficient, accurate, and less disruptive process for engineering teams and finance departments alike.
Getting started with Faros AI’s R&D Cost Capitalization module is easy. Request a demo today.
Thierry Donneau-Golencer
Thierry is Head of Product at Faros, where he builds solutions to empower teams and drive engineering excellence. His previous roles include AI research (Stanford Research Institute), an AI startup (Tempo AI, acquired by Salesforce), and large-scale business AI (Salesforce Einstein AI).
Stop guessing if AI token spend pays off. Faros Token Engineering traces coding agent usage to shipped features, incidents resolved, and ROI.
Product
7
MIN READ
Inside Faros Token Engineering: AI Spend Observability
Go beyond token usage with AI spend observability that shows where spend goes, what work ships, and the cost per verified outcome across teams.
Product
7
MIN READ
Inside Faros Token Engineering: AI Route Optimization
Optimize AI coding by routing each task to the right model and harness, using benchmarks from your own merged code to reduce cost per verified outcome.