Skip to main content

​
Consistency that scales

We create the building blocks for our consumers that are consistent, yet tailored to different roles and product areas. That consistency extends to ServiceTitan end users.

Consistent

We strive for consistency in everything we produce. From naming conventions and APIs to the look and feel of our components, we want to provide an experience for our internal and external customers that never feels disjointed.

Tailored

Our products, services, and documentation are crafted to support both designers and engineers in the spaces and toolchains they work in. We prioritize building adaptable resources that teams from all parts of the business can use in their domain.

​
Efficient and Sustainable

What we build solves immediate problems, but is built to last. We prioritize sustainable components and small iterations over edge cases and novel experiences. We don’t over-complicate our products or workflows.

Built to last

Our goal is to create solutions for common use cases, rather than focusing on a specific edge case or data type. Our components should adapt to specific product use cases, but should not be tied to any in a way that would make them obsolete as product needs change.We apply this both to our external offerings and our internal processes. Just as our components should be sustainable and adaptable, so too should our workflows.

Small iterations

We would rather release beta versions and minimum-viable products that we can get feedback and iterate on, versus building complex feature sets in isolation and delaying a release.

​
Built for everyone

We embrace the social model of inclusivity—we go beyond bare minimum requirements for accessibility. No user should feel left out when using our products, and we embrace inclusion in the way we work together.

Social model of inclusivity

While we do maintain a hard requirement of WCAG AA 2.2 accessibility compliance for the assets we produce, we consider that the floor rather than the ceiling. We reach for higher compliance levels where we can, and we take an empathetic approach to considering users from all backgrounds and contexts. This means thinking further than just people with disabilities—people from different cultural backgrounds, speaking different languages, working in different contexts, or on different devices.The key word is people. We often use the term users in our field, which is not wrong, but there are times that we need to acknowledge the personal and social side of who we are building products for.

​
Quality you can trust

Everything we create is validated, tested, documented, and fully-supported. We don’t cut corners, and we are quick to respond to questions and fix bugs. We over-communicate foundational and breaking changes.

Validated

We validate all new designs and features using a variety of research methods, such as user testing and competitive analysis, before they are added to our core libraries.

Tested

We follow a strict and comprehensive testing strategy for the code in our core libraries to prevent regressions and downstream bugs.

Documented

We are passionate about providing clear, role-focused documentation that has exactly the information needed to use our products and services.

Fully-supported

Our work doesn’t stop once a feature is shipped. We have clear communication channels, and are quick to respond to questions, requests, and bug reports.

​
Provide and Curate

We provide solutions for product teams, and have the expertise to curate contributions at any stage with a painless process. We value evolution over perfection, but strive for both.

Provide solutions

We build high-quality components and utilities to help product teams build faster, more efficiently, and with consistency and quality. Other teams can trust that we will provide the solutions they need for common use cases when building experiences for ServiceTitan users.

Expertise to curate

There may be features or ideas that product team designers and engineers have for the design system that we aren’t quite ready to build into the core system ourselves. This can happen when we are busy with other high priority work, or if the use case or solution could be too singular or unverified. To prevent isolated development and missed opportunities for contributions, we will provide a safe space for new ideas and features that is painless to use. Our team will handle the infrastructure and maintenance, so that contributors can focus solely on their contributions.As new features are added and iterated on, our team will help shepherd in meaningful additions to the core libraries. We have the expertise and experience to help with the evolution of contributions from ideas to stable additions that make our system stronger.

​
Anchor the core, enable the rest

Our design system provides a stable foundation for ServiceTitan’s core offerings. From there, we provide the tools, guidance, and flexibility to enable the rest of the business build, innovate, and thrive.

Stable foundation

Stable foundation ServiceTitan has a wide footprint that includes several apps and products. Our highest priorities as a team will always align with the company as a whole, and our core libraries reflect that. We aim to supply a solid, stable foundation for the most impactful areas of the business.

Enable the rest

Our primary focus is on ServiceTitan’s core products, but that doesn’t mean we ignore the rest of the business. We build our libraries in a way that allows for extending, customizing, and using the pieces that are most helpful to any specific product area. We may not have the capabilities to support every team due to technical or other reasons, but we will still provide the guidelines, documentation, and foundational tokens for teams to build with.
Last modified on January 23, 2026