Item: Ignition
Rating: 10
Author: Christopher Dulin

Use Cases and Deployment Scope

We began using Practice Ignition (PI) as part of a move toward value pricing. Primarily used by our 2 partners, including myself, it allows us to either collect payment upfront, spread our fee over multiple months at a flat rate, or collect payment sooner upon completion of work. We also use it to manage engagement letters and renewals of engagements. We have also found that it is useful in helping us project future cash flows. Our goal is to have 100% of our billing in PI. We are currently at about 60%.

Pros and Cons

Proposal process. PI makes it easy to create and send proposals to new and existing clients, collect their payment info, and get signature on the engagement letter.
Easily identify engagements that will be expiring, so we can begin to assemble a renewal.
Communication to and from the client during the proposal process, which keeps everything associated with the proposal together in one place.

The charge back process is messy and not transparent enough. When there is a charge back, PI deducts the amount from other payments settling on the same day, and does not provide a break down of the amounts. This makes it impossible to track without getting help from support.
PI should send email alerts monthly (or at some interval determined by user) for expiring engagements.
PI should allow the client to make service selections -- we should be able to offer 2 or 3 options under a service offering, and the client chooses and sees the impact on monthly/annual pricing.
PI should allow for more than 2 templates (Business and Individual).
PI should integrate with Jet Pack Workflow to automate the creation of new jobs once a proposal is approved.