Tasks · build · sales

B2B sales CRM with accounts, contacts, a staged deal pipeline, weighted forecast, and activity log

crm-sales-pipeline · 3600 s per turn · source

The ask

We're a nine-person consulting firm and I want one place for our client accounts, their contacts, and our deals, with the calls, emails, and meetings reps log on a deal showing on that deal and on the client's account. Our accounts, contacts, and pipeline are attached; they were kept in three separate spreadsheets, so there are duplicates, and I want each account and each person in there only once. Deals go Lead, Qualified, Proposal, Negotiation, then Won or Lost: nothing goes to Proposal without an amount and a contact, nobody marks a deal Lost without a reason, and the dashboard should show our pipeline weighted at 10, 25, 50, and 75 percent for those four open stages. Each rep sees only their own accounts and deals, our analysts can read everything but change nothing, and I look after the users and settings. Give me an admin login and a login for Leila Haddad, one of our reps.

Seed files the agent must import: accounts.csv</code>, <code>contacts.csv</code>, <code>deals.csv. The agent must leave a RESULT.json with a reachable URL, an admin login, and the named restricted login.

Acceptance checklist

26 binary items. The first 14 are the enterprise baseline shared by every build task (delivery, invitations, roles, server-side authorization, scoped live dashboard, exact lists and exports, audit metadata, validation, persistence); the rest are application-specific. Core items, which together define "first usable": 1, 3, 5, 6, 8, 14, 15, 22, 25.

The full checklist with per-item "how to check" instructions and expected figures is in checklist.md. Testers see it; the agent never does.

Change requests

Each change is a new one-shot turn on the carried-forward workspace. Only the owner's text below is sent; the tester items are withheld. After each change the full checklist is rerun, so regressions count.