Insightly for WordPress mirrors your account into custom tables. Opportunities live in insightly_opportunities with OPPORTUNITY_ID, OPPORTUNITY_NAME, PIPELINE_ID, STAGE_ID, OWNER_USER_ID, BID_AMOUNT, BID_CURRENCY, FORECAST_CLOSE_DATE, and OPPORTUNITY_STATE on every row. Pipelines and stages sit in insightly_pipelines and insightly_stages, users in insightly_users, organisations in insightly_organisations. The plugin admin lists everything by sync timestamp.

SleekView Kanban reads those tables and groups insightly_opportunities by STAGE_ID so each Insightly stage becomes a column. Stages render in the Insightly-defined order through the STAGE_ORDER column on insightly_stages. Card fronts show the opportunity name, owner from insightly_users, BID_AMOUNT formatted in BID_CURRENCY, organisation from the join, and FORECAST_CLOSE_DATE with overdue highlighting when the date is past.

Dragging from Qualification to Proposal updates STAGE_ID on the row and queues the change for the next Insightly push. OPPORTUNITY_STATE values Won, Lost, Abandoned, Suspended render with their own color cues. Each column header sums BID_AMOUNT so weighted pipeline reads at a glance, with currency aware formatting based on BID_CURRENCY per row when reps work across regions.

Insightly models opportunities with rich stage, currency, and ownership fields, and the WordPress mirror copies all of it faithfully. The gap is the view, because a flat list of opportunities does not communicate pipeline health and a sales team running off WordPress for content and demand-gen ends up jumping back to Insightly every time they want a board read. SleekView Kanban closes that gap.

Group by STAGE_ID and the team sees Insightly's stage order rendered as columns, drag an opportunity to Proposal and the change writes back to Insightly on the next sync push, embed the same board on a leadership dashboard and execs see weighted pipeline totals live. Currency-aware totals per column mean managers running multi-region teams open the kanban and read the right number without fighting an export. The result is one read of pipeline that lives inside the CMS that drives demand-gen, not a separate tab nobody wants to keep open and reconcile against the rest of the marketing stack.