Highrise CRM for WordPress mirrors your account into custom tables. Deals live in highrise_deals with id, name, status, price, currency, price_type, responsible_party_id, party_id, category_id, background, and updated_at on every row. People and companies sit in highrise_parties, users in highrise_users, deal categories in highrise_deal_categories. The default admin shows deals as a flat sortable list.

SleekView Kanban reads those tables and groups highrise_deals by status, which in Highrise is Pending, Won, or Lost. That gives a clean three-column board, with an optional fourth column for category-based grouping when the team uses category_id to model substages within Pending. Card fronts show the deal name, company or contact from highrise_parties, owner from highrise_users, price formatted with currency and price_type, and the category color.

Dragging a deal from Pending to Won writes the new status to highrise_deals and queues the change for the next Highrise API push. Lost deals can be filtered out by default with a saved view so the working board stays focused on Pending and Won. Column header totals sum price per status so the leadership read at the top of every week is the right one without exporting anything to a spreadsheet.

Highrise keeps its deal model deliberately simple: Pending, Won, Lost, plus an optional category for grouping. The WordPress mirror keeps the data faithful but stops at a flat list, which hides the very thing the model was designed to communicate. SleekView Kanban turns the same rows into the three-column board everyone expects, with price totals in every header, parties and owners joined for readable cards, and drag-and-drop that writes back to Highrise on the next sync push.

For teams that use category_id to model Pending substages, an alternate grouping renders a category-based board so the work-in-progress shape becomes visible. Embed the board on a leadership dashboard inside WordPress and execs read the pipeline shape live. Per-rep saved views give every seller a personal kanban URL.

The result keeps the calm Highrise model intact while delivering the read that a static synced list cannot give to anyone who is trying to run a sales week well from inside the CMS.