Best Setup for Weekly Account-Prioritization Workflow in Clay Using AI Scoring and Signals

Hi everyone - I’d love your opinion on the best setup for this in Clay. I’m currently building a weekly account-prioritization workflow for our Sales team focused on ICP accounts. The idea is to combine firmographic data with signals like hiring, news, and fundraising, then use AI scoring to identify which accounts should be prioritized each week. Right now, I have a main company table enriched with things like employee count, industry, description, country, locality, size, and LinkedIn URL. I then added signals via Tools, but as you can see in the screenshot, those signals are running into separate tables - which I honestly don’t fully understand. Would it make more sense to use lookups from those signal tables back into the main table for the AI scoring, or is there a better way to keep the signals directly in the main table? And is there any way to change the setup so the signals don’t run into separate tables in the first place? My goal is to keep this as low-manual-effort as possible. As a next step, I’d also like to build a small dashboard with Lovable + Clay Code to review these accounts weekly with Sales. Would love to hear how you’d approach this.