Skip to main content
This launch path outlines the typical path to launching embedded accounting in your existing product. This approach is best for organizations that prioritize accounting on their product roadmap. This implementation path scales for platforms supporting hundreds of thousands of businesses. If your platform is more interested in proving accounting demand with less than 1000 businesses, your product team will likely instead prefer Tight Ready-to-Launch Accounting.

​
Configure your SSO/authentication mechanism (1 day)

  1. Use your existing identity provider (e.g. Auth0, AWS Cognito, Okta, or Stytch) by following Tight’s user provisioning with existing identity provider instructions.
  2. Or, use custom code to provision Tight user accounts using the Tight API.

​
Design (2 days)

  1. Decide where to place the “Bookkeeping” navigation item inside your UX
  2. Preview and customize the branding/styling on the Business Owner Dashboard
  3. Receive your tailored theme from Tight for front-end developer use (see below)

​
Front-end Development (1 day)

  1. Add “Bookkeeping” navigation item to your existing product
  2. When your user clicks the “Bookkeeping” navigation item, get an access token and render the embedded end-to-end UX

​
Configure additional data integrations (post-launch)

Tight has many data integrations, including native integrations with popular financial platforms (e.g. Plaid, Stripe, Adyen) as well as custom integrations to ingest granular data already stored in your platform (e.g. invoices and line items stored in a Vertical SaaS platform, class hierarchies like cost centers, regions, locations, departments, etc.). The Tight team will create a custom implementation plan for your specific platform to ensure any financial data stored in your platform flows into your new accounting product. For example, the invoices tracked in your system are automatically reconciled with the bank deposits flowing into Tight.