A website visitor queue that remembers what you hide

Build me an internal app my SDR team opens every morning to work the companies Leadfeeder identified on our website. Today they scroll the raw Leadfeeder feed and re-hide the same irrelevant companies over and over, so the whole point of this app is that decisions stick: once someone hides a company, it never comes back into the queue for anyone.

The main screen is a Queue of companies identified in a date range I choose. Use Leadfeeder List Accounts once to resolve my Leadfeeder account id, then List Leads for the selected start and end date, and let me optionally scope the queue to one of my saved filters using List Custom Feeds, passing the chosen feed as custom_feed_id on the lead list. Each row shows the company name, industry, employee count, country and visit count from the lead record, plus the actual pages they read from List Visits For Lead. Give me filters above the queue for industry, employee-count band and pages viewed.

Leadfeeder's lead list requires both start_date and end_date, caps page size at 100, and the token allows only 100 requests per minute, so do not fetch visit detail for every lead up front. Load the lead list first and fetch List Visits For Lead lazily for the rows currently visible, caching what has already been pulled. Use Get Lead when I open a single company for the full detail view.

Rank the queue by intent, not just visit count. A company that viewed pricing, demo or product pages should rank above one that only read a blog post, and the high intent pages should show as badges on the row so the SDR can see why it sits near the top.

Every row has Keep and Hide buttons. Hide is remembered by the app itself, in its own stored list keyed by the Leadfeeder company, and hidden companies are filtered out of the queue on every later load, for everyone on the team. A separate Hidden tab lists everything hidden, with who hid it and when, and an Un-hide button that returns the company to the queue. Keep marks the row as worked so it drops out of the active queue without being permanently suppressed.

Before offering to create anything, check Salesforce. For the companies in the visible queue, use Get Many Accounts to look for an existing account matching the visitor by company name and website domain. If one matches, show the account name, its owner and a link to the record inline on the row, and do not offer to create a lead for it. Instead offer an Add Note to Account button that logs the visit and the pages they read onto the existing account, so an account already in play gets the signal without a duplicate record.

Each unmatched row has a Find the buyer button that kicks off a background agent for that one company. The agent uses Apollo People Search to find people at that company in the job titles I target, which I configure in app settings, then People Enrichment on the best two or three to get contact details. It also reads that company's visits and writes a short why-now summary grounded in the specific pages they viewed, for example that they hit pricing twice and then the integrations page. Its output lands back on the row as a review card the SDR can open, so the queue always shows which companies have buyers found and which are still untouched.

Nothing is written to Salesforce until I approve the card. On approval, use Create Lead for the chosen contact, carrying the company details and the why-now summary onto the lead, then Create Task for the follow-up assigned to the right owner. Resolve the owner with Get Many Users and Get Many Accounts: if the company already maps to an account, use that account's owner, otherwise let me pick from the user list with a default owner I set in settings. Leadfeeder's own CRM sync is known for silently assigning the wrong owner, so always show the owner the app picked on the approval card and let me change it before anything is created.

Design it for a five minute morning pass: one decision per row, keyboard friendly, and a counter showing how many companies are still left to triage for the selected range.