Reading through Fawn Dooley’s approach to building Salesforce foundations, it seems incredibly thorough. The emphasis on bridging design systems with tokens and ensuring mobile-first accessibility from the very first commit is exactly what distributed teams need. I appreciate that she handles both the Apex integrations and the UX decisions, ensuring the shipped product feels like a real app rather than bolted-together legacy code. It looks like a robust strategy for long-term consistency.
What reviewers say about Fawn Dooley · Front-End Architect
What is Fawn Dooley · Front-End Architect?
Fawn Dooley is a front-end architect and independent consultant based in San Francisco who specializes in Salesforce-related projects. She builds design systems, design tokens, and component patterns for distributed enterprise teams. Her work spans the full stack of a Salesforce experience, including Apex and API integrations, data modeling, and translating data into customer-facing workflows.
Who is this service for and what industries does it serve?
The business serves distributed enterprise teams that need to build on a solid foundation for Salesforce experiences. It targets clients working with Salesforce Platform & Experience, design systems, and mobile-first interfaces. The foundation is set once and right to ensure consistency and speed for the team.
How can a potential client get started or book a consultation?
Clients can start by visiting the website at followingfawn.com to see how the architect works and what she builds. The process involves bridging platform design systems like SLDS with client brand systems using tokens and reusable component patterns. Teams can also engage her for Apex + design system + experience API integration and UX decisions.
What specific features and products are offered?
The architect emphasizes responsive, accessible, mobile-first interfaces as a core feature of the service. She bridges platform design systems such as SLDS with client brand systems to create consistent experiences. The service also includes AI-accelerated UI development while maintaining a clean, maintainable system.
How long has the architect been in the industry and what is her background?
The architect has 12+ years in consulting and has worked on 30+ enterprise programs across 15+ industry verticals. She has a history of building across the full stack, including Adobe AEM component development and enterprise Java commerce. Her experience includes native iOS app development shipped to the App Store in 2011.
What are the key principles guiding the design and development process?
The service focuses on making mobile-first and accessibility non-negotiables from the first commit. This approach ensures the interface is not a retrofit at the end but is built correctly from the start. The architect also turns a data model into a customer workflow by deciding what is primary and secondary.
How does the architect handle AI tools and integration partnerships?
The architect helps teams choose the right tools for AI-accelerated UI development while holding the quality line. This ensures velocity produces a maintainable system instead of a mess of one-off components. The service also involves partnering with integration teams on the middleware they own for API integration.
What specific technical tasks are performed for Salesforce integrations?
The architect writes Apex that connects the Salesforce Platform to enterprise APIs, such as consuming MuleSoft-exposed services. She wires Data Cloud into the experience and maps raw payloads into UI that makes sense. This involves building the consuming side end to end for a seamless experience.
How are design systems and tokens managed to ensure consistency?
The architect emphasizes fighting neither the platform nor the brand when bridging design systems. She applies tokens like var(--), never hardcoded hex, and reusable component patterns to stop rebuilding the same things. This ensures the foundation is solid, so everything built on it stays consistent.
What problems does the service aim to solve for its clients?
The service aims to prevent rework, drift, and desktop-only UI in a mobile-first world. When the foundation is solid, the team moves fast without needing to rebuild the same things on every project. The architect owns the foundation to ensure the team never ships a desktop-only UI.
What tools and platforms are used in the development process?
The architect works with a variety of tools and platforms, including Salesforce, MuleSoft, and Data Cloud. The service includes Apex + design system + experience API integration and component patterns. The architect also partners with integration teams on the middleware they own for a full-stack solution.
What is the official website of Fawn Dooley · Front-End Architect?
The official website of Fawn Dooley · Front-End Architect is followingfawn.com.
How is Fawn Dooley · Front-End Architect rated on Trustburn?
On Trustburn, Fawn Dooley · Front-End Architect has a rating of 4 out of 5 based on 5 reviews.
Post your question publicly — other visitors, and whoever manages this page, can answer. It will be visible on this page.
Want to hear about this company again? Follow it and we’ll email you when a new review appears.
Based on reviews, listing data and the company's website. Verify anything important with the company directly.
Fawn Dooley positions themselves as a Front-End Architect specializing in Salesforce, which is a very specific niche. The emphasis on design systems, tokens, and mobile-first approaches is certainly appealing for teams struggling with desktop legacy UIs. The claim of owning the foundation from Apex to the experience layer suggests a deep technical understanding. However, the description is heavily focused on technical implementation details rather than business outcomes or client success stories. While the mention of 12+ years in consulting and 30+ enterprise programs lends credibility, the lack of specific case studies makes it hard to verify the quality of the work. The approach of bridging design systems and handling API integrations is robust, but for a neutral assessment, one would need more evidence of how these technical decisions translate to user satisfaction. It feels like a strong technical resource, but perhaps less clear on the strategic value for non-technical stakeholders. The focus on 'not bolted together after the fact' is a good differentiator, yet the overall offering remains somewhat abstract without concrete examples of past projects.
The structured workflow for Salesforce experience building seems very logical and clear from the available information.
The detailed work breakdown looks promising. Does the pricing include the full design system setup, or is that billed separately?
The scope seems comprehensive, covering Apex, API integrations, and design systems. However, the lack of explicit pricing structures for these distinct layers creates uncertainty. Without clear breakdowns, it is difficult to assess whether the cost aligns with the specific deliverables promised to enterprise clients.
Questions & Answers
No questions yet — be the first to ask.
Sign in to post
Your text is saved — you'll come right back to post.
Don't have an account? Create one
News & Press
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
About Fawn Dooley · Front-End Architect
Fawn Dooley is a front-end architect based in San Francisco who works as an independent consultant on Salesforce-related projects. She specializes in building design systems, design tokens, and component patterns for distributed enterprise teams. Her work spans the full stack of a Salesforce experience, including Apex and API integrations, data modeling, and translating data into customer-facing workflows. She emphasizes responsive, accessible, mobile-first interfaces and bridging platform design systems such as SLDS with client brand systems.
- Website
- followingfawn.com
- [email protected]
- Categories
- Information technology and services
