// core.philosophy
How We Think About Accounting for Technology Companies
Precision isn't a differentiator — it's the baseline expectation. What varies between accounting firms is the depth of understanding behind that precision, and what they do with it.
← Back to Home// foundation
What we're built around
Synthfin exists because there's a gap between what technology companies need from their accounting and what most accounting firms are designed to deliver. Subscription billing, R&D credit frameworks, and equity compensation programs are each complex enough to warrant genuine specialization — not competent generalism applied to a different context.
Our foundation isn't a mission statement. It's a structural choice: we built everything — services, processes, documentation templates, and institutional knowledge — around the specific accounting demands of the technology sector. That constraint is intentional, and we think it produces better work.
// philosophy
Depth before breadth
There's a version of this business that serves every industry and bills itself as a full-service firm. We deliberately chose not to build that. Three well-defined services, applied with genuine depth, produce more value for the clients we serve than twenty services applied with adequate competence.
That philosophy shapes every decision we make — what to take on, what to decline, and how to structure the work we do.
// vision
Accounting that doesn't need to be redone
The goal for every engagement is simple: produce work that holds up. Revenue schedules that don't need reconstruction before audit. R&D documentation that captures what it's supposed to capture. Equity disclosures that your auditors and investors can review without follow-up questions about methodology.
That's not an ambitious vision — it's the minimum acceptable standard. We work to make it the consistent outcome.
// core.beliefs
What we actually believe
belief_01
Context changes everything in accounting
A deferred revenue balance on a SaaS company's books is fundamentally different from deferred revenue in a professional services firm. The standard is the same; the judgment required to apply it correctly is not. Context isn't a background factor — it's the core variable that determines whether accounting output is useful or misleading.
belief_02
Documentation is the actual deliverable
The calculation matters. The schedule that supports it matters more. Accounting output that can't be reviewed, traced, or audited isn't complete — it's a liability waiting to surface at the worst possible time. We treat documentation as the primary deliverable, not the administrative appendix to the "real" work.
belief_03
Scope clarity protects both parties
Undefined scope benefits neither the client nor the firm. A written scope agreed before work begins sets accurate expectations, prevents the engagement from drifting into undefined territory, and gives both sides a clear reference point when questions arise mid-project. We won't start work without it.
belief_04
Specialization is a service, not a constraint
Being narrow about what we take on isn't a limitation — it's the mechanism through which we maintain quality. When we tell a prospective client that their needs fall outside our three areas, that's not a failure. It's the system working as intended: we do specific things well rather than many things adequately.
belief_05
Published pricing is a form of honesty
Pricing that requires a proposal and negotiation puts the client at an information disadvantage. Our service rates are stated publicly. That doesn't mean every engagement is identical — scope shapes cost — but it gives prospective clients a genuine starting point rather than a figure adjusted to whatever the conversation suggests they can bear.
belief_06
Cross-functional accounting is better accounting
R&D credit documentation done entirely within the finance team will miss activities that engineering teams consider routine. Equity accounting that doesn't touch the HR or legal team misses grants, modifications, and terminations that change the numbers. Accounting that stays in its lane produces incomplete output.
// principles.in.practice
How these beliefs show up in the work
belief → practice
Context changes everything
Before we calculate anything, we ask how your billing actually works. Subscription tiers, usage-based components, implementation fees, and professional services layers within a single contract each get treated differently under ASC 606. We map the structure first — then apply the standard to the actual arrangement, not a simplified version of it.
belief → practice
Documentation is the deliverable
Every engagement includes supporting schedules structured for external review. Revenue recognition includes a deferred revenue rollforward. R&D credit work includes a contemporaneous activity catalog. Equity accounting includes a vesting schedule reconciliation and disclosure draft. These aren't attachments — they're the output.
belief → practice
Scope clarity protects both parties
The initial assessment produces a written scope document. It describes what's included, what's excluded, what the deliverables are, and what the timeline looks like. That document is agreed before any billable work begins. If the scope needs to change mid-engagement, we flag it and discuss it — not absorb it silently into the final invoice.
// human.centered.approach
The person behind the accounting question
Finance teams aren't all CFOs
Many of our clients are heads of finance at early-stage companies, controllers at growth-stage businesses, or founders who've taken on the finance function directly. The accounting is the same regardless — but the context around it isn't. We adjust how we explain our work, what level of detail we include in deliverables, and how we structure communication to fit the person on the other end.
Questions are useful signals
When a client asks a question that suggests they're uncertain about something, that's information — not an interruption. It either means we haven't explained something clearly, or it reveals a complexity in their situation that changes how the work should be done. Either way, it's worth taking seriously. We don't produce output and then make ourselves hard to reach.
// innovation.through.intention
How we stay current without chasing trends
Standard evolution
ASC 606, ASC 718, and IRC §41 aren't static. Interpretive guidance, FASB updates, and IRS rulings change how specific situations should be treated. Staying current in three areas is genuinely manageable — staying current across twenty is not.
Business model changes
SaaS billing structures evolve. Usage-based pricing, hybrid subscription models, and consumption tiers create new accounting questions regularly. Because we work exclusively in this space, new patterns surface in our client base before they become industry-wide problems — and we develop treatment positions early.
Template refinement
Each engagement surfaces edge cases that improve our templates. A deferred revenue schedule updated to handle a new contract structure becomes the template for the next client with a similar structure. The work compounds across engagements in a way that benefits everyone we work with.
// integrity.transparency
What we mean when we say transparent
pricing
Rates are published, not negotiated
SaaS Revenue Recognition: $3,500/month. R&D Tax Credit Documentation: $4,000. Equity Compensation Accounting: $2,800. These are the rates. Scope shapes the total engagement cost — complexity and volume affect the hours — but the rate itself isn't a variable we adjust based on who's asking.
scope
What's included is written down
Before work begins, the scope document describes deliverables, exclusions, milestones, and timeline. It's not a contract designed to protect us legally — it's a communication tool that prevents the engagement from becoming something neither party intended.
fit
We say no when it's the right answer
If a prospective client's needs fall outside our three areas, we tell them that — and often point them toward a firm better suited to their situation. Taking on work that isn't a good fit produces worse output and ties up capacity that should go toward work we're genuinely built for.
changes
Mid-engagement changes are flagged, not absorbed
When something changes the scope of a project — a new billing structure surfaces, an equity grant introduces a modification accounting question — we flag it explicitly, discuss the implication for timeline and cost, and agree on how to proceed. It doesn't appear as a line item on the final invoice with no context.
// collaboration.model
Accounting as a cross-functional activity
The accounting standards that govern SaaS revenue, R&D credits, and equity compensation all require information that lives outside the finance function. Recognition of a software contract's components requires knowing what engineering is delivering and when. R&D credit documentation requires understanding which projects involved qualified research — which engineering and product teams know better than anyone. Equity accounting requires knowing when grants were made, modified, or forfeited — which HR and legal typically track.
The accounting itself is a finance function activity. Producing it correctly requires the accounting firm to have access to and communication with the teams that hold the relevant information. We build that coordination into how we work, not as an escalation when something goes wrong.
with engineering/product
R&D activity identification, qualifying expense documentation, delivery milestone tracking for multi-element contract recognition.
with HR/legal
Equity grant records, modification events, termination-related forfeiture tracking, ESPP enrollment and purchase data.
with your auditors
Supporting schedule format aligned to audit expectations, available for direct auditor questions after delivery.
// long.term.thinking
Accounting that compounds rather than resets
The problem with starting over
Many companies switch accounting firms and discover that the new firm needs to reconstruct prior-period schedules before they can do current-period work. Deferred revenue balances don't carry over cleanly. Equity vesting history needs reconciliation. R&D documentation from prior years may not meet current credit requirements.
This reconstruction cost is real and often underestimated when switching relationships. It's one reason we structure deliverables to be portable — in a format that a successor firm or auditor can pick up without needing us to explain the history.
What continuity produces
When the same team works on the same accounting area over multiple periods, the quality of the output improves in ways that are hard to invoice for separately. The deferred revenue rollforward from Q1 becomes the starting point for Q2 without reconciliation overhead. The R&D activity catalog from year one is the baseline for year two's additions and exclusions.
That continuity reduces friction, reduces the chance of error at period transitions, and reduces the time we need to spend orienting ourselves before doing the actual work.
// what.this.means.for.you
What to expect when you work with Synthfin
-
A written scope before work begins
Every engagement starts with a defined scope document. Deliverables, exclusions, timeline, and rate — agreed in writing.
-
Deliverables structured for external review
Schedules and documentation formatted for your auditors from the start — not reformatted after the fact.
-
Access after delivery
We stay available for auditor questions and follow-up analysis after work is delivered. The engagement doesn't end at file transfer.
-
Transparent rate structure
Published rates on all three services. Scope determines total cost — the rate isn't a variable adjusted per prospect.
-
Direct communication when scope changes
If something changes mid-engagement, you hear about it explicitly — with the implication for timeline and cost — before it happens.
-
A clear answer if we're not the right fit
If your needs fall outside our three service areas, we'll tell you that directly rather than take on work we're not built for.
// work.together
If this approach fits how you want to work
The starting point is a conversation about your accounting structure and what you're working on. We'll tell you whether it falls within our areas and what an engagement would look like — no ambiguity, no process.
Get in Touch