Build a CRM on Rails

Build me a brand-new Ruby on Rails CRM from scratch with Avo 4 as the management UI (https://avohq.io, docs at https://docs.avohq.io/4.0/). I have no app and no schema yet, so scaffold the whole thing.

1. Generate the application with rails new using PostgreSQL, then set up sign-in with Rails' built-in authentication generator (bin/rails generate authentication) so there is a real User behind the login. Add the avo gem to the Gemfile, bundle, run bin/rails generate avo:install, and mount Avo at /avo so it sits behind that authentication and only signed-in users reach it.
2. Work out the data model before touching a migration. A CRM lives or dies on how it represents the people and accounts a team sells to, the deals moving through a pipeline, and the running history of calls, notes, and emails logged against them. Decide from first principles which entities this genuinely needs, whether a deal's pipeline position is best as an enum on the record or a stages table of its own, and how everything associates: who a deal belongs to, which contacts sit under a company, where an activity attaches. Write that plan down, then generate the migrations and models to match. Treat those CRM concepts as ground the design has to cover, not a schema to transcribe.
3. Generate an Avo resource for each model with bin/rails generate avo:resource (https://docs.avohq.io/4.0/resources.html). Set self.title to the label a rep would recognize, list the associated tables in self.includes so the Index view does not fire a query per row, and give self.search a query over the columns someone would actually type, like a contact name or company. Match every field to the column you chose: text and text/textarea for names and notes, date_time for timestamps, select backed by the enum for a deal stage or status, belongs_to and has_many for the associations so contacts, deals, and their activity render as linked screens.
4. Turn the pipeline verbs into Avo Actions: marking a deal won or lost, reassigning its owner, logging an interaction against a contact. Since the app is new, put the real behavior in model methods or small service objects and have each action call into that, so the business logic lives in one testable place instead of inside the action. Add filters and scopes for the slices reps live in, such as open deals, my accounts, or overdue follow-ups, and point each scope at a model scope so the query is defined once.
5. Add a dashboard with metric and chart cards for what a sales team watches day to day, pipeline value by stage and deals closing this month among them, built from the models you settled on (https://docs.avohq.io/4.0/dashboards.html).
6. Authorize with Pundit policies so a rep only sees and edits the accounts and deals they own while a manager sees the whole book, and the same rules gate the actions so a rep cannot reassign a deal that is not theirs (https://docs.avohq.io/4.0/authorization.html).
7. Seed realistic sample data: a handful of users across both roles, companies with contacts under them, and deals spread over every stage with a few logged activities, so every Index view, filter, and dashboard card has something real to show.
8. Boot the app, sign in, open /avo, and confirm the loop works end to end: browse to a company, open one of its deals, move it to a later stage with your Mark won action, and watch the pipeline dashboard update.