Build internal tools on Rails

Build a new Ruby on Rails application whose back office runs on Avo 4 (https://avohq.io, docs at https://docs.avohq.io/4.0/). There is no existing app or schema yet, so you are creating both the business data this company operates on and the internal tools the team uses to run it.

1. Generate the app with rails new using current defaults, then wire up sign-in with bin/rails generate authentication so there is a real User and session behind everything. Add the avo gem, bundle, run bin/rails generate avo:install, and mount Avo at /avo so it sits behind that authentication.
2. Design the domain before touching migrations. This is a company's back office, so reason from first principles about what such a business actually operates on: the customer accounts it serves, the people inside them, the orders or subscriptions that generate revenue, the payments and refunds against those orders, and the support conversations the team fields. Decide which lifecycle states belong on a record as an enum (an account that is trialing, active, or suspended) and which deserve their own table (a payment with its own history). Map the associations, then write the migrations once the shape holds together.
3. Give every model an Avo resource with bin/rails generate avo:resource. Match each field to the column you designed: a select over an enum, a badge over a status, a money field for revenue and refunds, date_time for timestamps, and belongs_to and has_many for the associations. Set self.title to something a person reads, self.includes for the associations you render so the lists stay fast, and self.search over what support actually types, a name, an email, an order number (https://docs.avohq.io/4.0/resources.html).
4. Turn the operational verbs into Avo Actions: issue a refund, extend a trial, suspend an account, close a ticket. Because the app is new, write the logic these actions need as model methods or small service objects, then have each action call one, ask for confirmation, and run as the signed-in admin so the change is attributable.
5. Add filters and scopes for the queues each team lives in, trialing accounts, past due invoices, open tickets, so anyone lands on the right list without SQL. Give ops a dashboard with the numbers they watch, signups this week, MRR, open ticket count, using metric and chartkick cards (https://docs.avohq.io/4.0/dashboards.html).
6. Authorize with Pundit policies per team so support, finance, and ops each see and change exactly their slice, and an admin sees everything (https://docs.avohq.io/4.0/authorization.html).
7. Seed realistic sample data: a spread of accounts across every status, users under them, orders and payments with a few refunds, and open and closed support tickets, so every screen, filter, and dashboard card has something to show.
8. Boot the app, open /avo, and confirm the workflow end to end: search an account by email, run Extend trial on it, and watch the change land without a console session.