Skip to main content
This implementation plan outlines the typical path to launching human-assisted bookkeeping in your product. Each section is titled after the role/job function that would typically complete the underlying steps:

Planning/administrative (1 day)

  1. Curate your default Chart of Accounts template
  2. Configure your bank linkage integration
  3. Configure your automated email domain

Design (1 day)

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

Development (2 days total)

Back-end (1 day)

  1. When a business opts into your new Bookkeeping product, create their company in Tight
  2. If you are using Tight’s Ready-to-Launch product, the API response contains the readyToLaunchUrl that you can simply return to your front-end and redirect your user to
  3. If you’re not using Ready-to-Launch, create an endpoint to get a short-lived UI access token (no need to store in DB)
    If you use Auth0, AWS Cognito, Okta, or Stytch, you can skip the above back-end development steps by using your existing identity provider.

Front-end (1 day)

  1. Add “Bookkeeping” navigation item to your existing product
  2. When your user clicks the “Bookkeeping” navigation item:
    1. Get an access token from your back-end (see above)
    2. Redirect your user to the Ready-to-Launch page
    3. Or, Embed the Business Owner Dashboard using the access token and theme
      This dashboard presents the owner-operator with only the info that they need to see, such as transactions the bookkeeper needs input on.

      It additionally includes a sub-navigation menu for power users to access granular functionality, such as the full transactions dashboard, mileage tracking, income taxes, etc.

      If your product already has a well-defined navigation structure, you can disable the sub-navigation inside the Business Owner Dashboard and utilize your own navigation.

GTM

  1. Roll out your Bookkeeping Product in a phased approach
    1. 10 users: work directly with users to onboard them and get feedback
    2. 100 users: test automated onboarding flows (e.g. UI-based onboarding call scheduling), Tight-led CoA iteration based on transactional data, and build confidence in bookkeeping operations
    3. 1000 users: Vertical-specific learnings/efficiencies generated for Tight algorithms and bookkeepers
  2. Provide top-tier Support
  3. Productization/pricing strategy