Lookout
See a signal. Start the next move.
Lookout is the signal automation platform built around Motion: when an account or customer signal fires, evaluate the conditions and run the right action.
lookout.sanka.com
Lookout
Search
NotificationSupport
Mayu KawasakiSanka Inc.
Mayu KawasakiSanka Inc.MotionsHealthData streamsSettings
Active MotionsSignal → decision → action+ Create Motion
Funding news outreachFunding news→Research → Email42
High-intent site visitPricing page→Score → Route owner31
Champion job changeRole changed→Approve → Reconnect18
Funding news outreach
SignalFunding news→
AI decisionICP + timing→
ApprovalSales owner→
ActionResearch + email
Runs42Approved94%Pipeline¥8.4M
Signal→Conditions→Motion→Action→Measured outcome
GTM automation
When a signal fires,
run sales and marketing.
Motion is the core of Lookout. It watches account and customer signals, checks who they apply to, and runs the right action—with approval where your team needs it.
LinkedIn & content
Inbound & operations
ABM & ads
Expansion & retention
AI-native plays
Measure the whole journey
Collect first-party events with Sanka Tag and connect campaigns, pages, leads, opportunities, and orders.
Find the leak
See where spend stops turning into pipeline, where conversion drops, and which channels only look busy.
Move with evidence
Give every team the same attribution view, then shift budget and follow-up toward what compounds revenue.
Attribution you can inspect
Every number keeps its trail.
Lookout preserves the path behind each conversion instead of hiding it inside a score. Trace the source, campaign, session, account, opportunity, and revenue event.
1
Google Ads / brandIdentity preserved
2
Pricing page · 04:18Identity preserved
3
Demo requestIdentity preserved
4
Opportunity · ¥2.4MIdentity preserved
5
Closed wonRevenue attributed
Weekly opportunity briefReady
Move 12% of partner spend to high-intent search.
Partner traffic grew, but opportunity conversion fell 31%. Branded search created 2.4× more qualified pipeline per yen this week.
From dashboard to decision
Know the next move—not just the last result.
Lookout turns changes in traffic, conversion, pipeline, and revenue into a prioritized brief your team can review and execute.
Why Lookout
More tools still leave work between them.
Lookout is the AI-native operating layer for signals, decisions, and action. It works across the stack you already have, runs Motion continuously, and keeps people in control of policy and approvals.
| Compared with | Lookout | More hires | Point AI tool | Agency | Build internally |
|---|---|---|---|---|---|
| Watches every signal continuously | Always on | Manual coverage | One signal | Service scope | You maintain it |
| Connects data, identity, and routing | One operating layer | More handoffs | Another silo | Runs outside | Long build |
| Builds and runs repeatable Motion | Trigger to action | Playbooks by hand | Single task | Campaign delivery | Custom project |
| AI execution with human control | Policies + approvals | Human only | AI without workflow | Depends on team | You build both |
| Measures outcomes and improves | Closed-loop | Separate reporting | Activity metrics | Periodic reports | More engineering |
| Keeps the system inspectable | Rules and trails | Tribal knowledge | Vendor logic | Opaque process | Owned, if shipped |
Built on first-party data
Fresh data. Rebuildable attribution. No black box.
Sanka Tag
Collect browser events from allowed origins with workspace-scoped delivery.
Data streams
Monitor collection, export lag, duplicate rates, and destination health.
Attribution rebuilds
Preview and rebuild attribution when models or source data change.
Questions, answered
What teams ask before they put Lookout to work.
Start with one Motion, prove the signal-to-outcome loop, then expand across channels and teams.
01What does Lookout actually do?
Lookout watches business and customer signals, evaluates conditions, and runs a reusable Motion—from research and routing to outreach and measurement.
02How is it different from an AI SDR?
An AI SDR usually handles one outbound channel. Lookout is the operating layer underneath: it connects signals, records, decisions, approvals, actions, and outcomes across your stack.
03Is this a service or software?
Lookout is software. AI continuously monitors, researches, drafts, routes, and executes the work you define; your team owns the policies, approval gates, and final operating model.
04Does it replace our CRM or warehouse?
No. Lookout works with your existing system of record and tools. It adds the signal-to-action layer instead of forcing a rip-and-replace project.
05How autonomous is it?
You choose. Low-risk actions can run automatically, while sensitive outreach, budget changes, or record updates can require human approval before execution.
06Which signals can start a Motion?
Sanka Tag events, workspace record changes, scheduled checks, and connected external signals can all enter the same signal envelope and trigger a Motion.
07How does Clay connect to Lookout?
Connect Clay's HTTP API in Lookout settings, test the connection, then map a Clay signal to a Motion. Clay API availability depends on your Clay plan or trial.
08What do we install?
For website behavior, install Sanka Tag directly or through GTM. Lookout provisions the managed workspace data plane and handles the event stream behind it.
09Can we inspect and rebuild attribution?
Yes. Source events and identity trails remain inspectable, and preview-first rebuilds let you check model or source-data changes before a confirmed run.
10Can we start small?
Yes. Create a workspace, start with one Motion and an internal or first-party signal, and add paid external connectors only when the use case is proven.