SeerShark
Get updates by email

Your watchlist, watched for you.

Know what changed on your watchlist, and why.

SeerShark is building a watchlist platform that explains setup changes with their supporting context. Sign up for development updates and future access news.

SeerShark is in development. Signing up does not create an account or grant product access.

Preview build: this form does not send or save anything.

Watchlist · FridayData through 10:00 ET
  • META21 EMA Pullback
    Conditions Ready

    Setup conditions met at the 10:00 close.

  • NVDA21 EMA Pullback
    Conditions not met

    The 10:00 bar didn’t close above Thursday’s high.

  • MSFT21 EMA Pullback
    Waiting

    No pullback yet.

    Tight-Base Breakout · Preview
Viewing time 10:08 ETDemonstration · Simulated data
Setup change10:00 ET

META · 21 EMA Pullback

Conditions Ready

Setup conditions met. The 10:00 bar closed above Thursday’s high.

Simulated alert preview — not a real notification

How it is being built to work

Three moments, one watchlist.

SeerShark is being built around the moments a trader already has: choosing what to follow, noticing that something changed, and coming back to it later.

Keep

Keep a watchlist

Choose the stocks you follow. Each one will show the state of its setup in plain words, checked on finished bars.

Understand

Understand a meaningful change

When a setup changes, its explanation will say which rule isn’t met, if any, and what needs to change.

Review

Review its supporting context

Changes will be saved with the time their data runs through. A correction will be added beside the original, which stays as it was saved.

The platform

Each state names its own cause.

A simulated view of META on 21 EMA Pullback, the first playbook being built. Its checks run on finished bars, and a snapshot is saved when a change is recorded.

Watchlist / META / 21 EMA Pullback Demonstration · Simulated data

META · 15-minute bars · Thursday and Friday morning, ET · simulated

META · 21 EMA Pullback

Conditions Ready

Setup conditions met at the 10:00 close.

All three checks are met on finished bars:

  • The daily setup heldDaily
  • The bigger trend is confirmed30m
  • The 10:00 bar closed above 342.6015m
Data through10:00 ET
Saved at10:00:02 ET
Viewing time10:08 ET
Watchlist updatesNewest first

NVDA · Correction. The 10:00 bar’s close was corrected from 176.10 to 176.02. The evidence changed, the result did not.

META · Conditions Ready. Setup conditions met. The 10:00 bar closed above 342.60.

Which rule isn’t met?

Understand the unmet rule and what could satisfy it.

Full checklist

Which conditions are met, what needs to change, and when the setup is checked next.

Snapshot

Revisit the information known when a change was recorded.

Replay

Review changes and separate the original view from the corrected view.

NVDA · 21 EMA Pullback

Conditions not met

Which rule isn’t met?The 10:00 bar didn’t close above Thursday’s high.

What needs to change?One finished 15-minute bar closing above 176.40 while the bigger trend stays confirmed.

Demonstration · Simulated data

From the SeerShark demonstration

A Snapshot from the simulated demonstration, separate from the examples above.

Snapshot of NVDA saved at 10:03:12 ET on Friday 14 August: the daily setup check met, the 30-minute trend check supportive, the 15-minute structure check not met, and the next check at 10:15 ET. Demonstration with simulated data.Snapshot of NVDA saved at 10:03:12 ET on Friday 14 August: the daily setup check met, the 30-minute trend check supportive, the 15-minute structure check not met, and the next check at 10:15 ET. Demonstration with simulated data.

Snapshot

In development

Saved when the setup changed. It shows the information available when the change was recorded; later corrections appear separately.

Demonstration · Simulated data
Roadmap

What is being built, and what may come after.

Stages describe what exists today, not when anything will be released.

We’re building five core types of setups, starting with Trend Pullback and Tight-Base Breakout. More variants can follow within each type. Our plan for the first customer release requires all five types, tested and usable by its first users. Customer access isn’t open and no release date is announced.

In development Being built now, and next in line. The Core workflow, Trend Pullback and Tight-Base Breakout

Core workflow

In development

  • Watchlist

    Follow chosen stocks and see what changed.

  • Setup explanations and Full checklist

    Understand the unmet rule and what could satisfy it.

  • Snapshot

    Revisit the information known when a change was recorded.

  • Replay and Watchlist updates

    Review changes and separate the original view from the corrected view.

  • Notifications

    Know that a recorded setup changed.Production delivery is in development and email is planned. Notifications can be delayed or missed. Check Watchlist updates for recorded changes.

Setup types in development

A playbook is a set of checks for a stock pattern. SeerShark is being built around five core setup types, each watched by one or more playbooks.

In development

Trend Pullback

Watch a pullback toward a trend average.

21 EMA Pullback is the first playbook being built.
In development

Tight-Base Breakout

Watch a move above a narrow trading range.

Next in line.
Planned What we’re planning to build. Three setup types, four tools, education and watchlist counts

Planned setup types

Planned

Support/Resistance Flip

Watch whether former resistance becomes support.

Planned

Power-Gap Pullback

Watch a pullback after a large upward gap.

Planned

Failed Break & Reclaim

Watch a break of a level that does not hold, and the move back across it.

Planned tools and features

5m Timing, Thermal and Tide Table follow the Core workflow. Volume Pulse is planned alongside the playbooks, separate from Core. None of these changes how setups are checked.

Planned

Education and tutorials

Learn how stock playbooks work and how to read them in SeerShark, through videos and written guides.

Three written lessons exist today; the rest of the library is planned.
Planned

Watchlist counts

See how many SeerShark watchlists a stock is on, in bands.

A proposal, not a committed build.
Exploring Ideas we’re exploring. Gamma Current, Deepwater, Reef Infrastructure and Echo AI

Nothing here is available to customers. Customer access is not open.

SeerShark development updates

Follow the build.

Development updates and future access news from SeerShark, by email.

SeerShark is in development. Signing up does not create an account or grant product access.

  • Asks only for your email address
  • Occasional updates
  • You confirm by email
  • Unsubscribe from any update

Preview build: this form does not send or save anything.

What you’re signing up for.

You’ll get

  • Development updates: what was built, what changed in the plan, and what’s next.
  • Future access news, when there is something you can use.
  • Occasional emails. Every one has an unsubscribe link.

Signing up doesn’t mean

  • An account, product access or a reserved place.
  • A release date. None is announced, and customer access isn’t open.

Privacy

We use your email address only to send these updates. Every update email has an unsubscribe link, and you can ask for your address to be deleted. Cloudflare hosts this page and runs its bot check.

Read the full privacy notice
What it’s used for
Sending the SeerShark development updates and future access news you asked for.
What the form sends
Your email address and the campaign tags in this page’s address, such as the platform and post you came from. The email service receives both, along with your IP address, which it uses to estimate your location and to check that sign-ups are genuine. The form also sends a one-time code from the bot check, which only Cloudflare reads.
Where the page runs
On Cloudflare. From there, your email address goes on to the email service, and this site keeps no copy of it.
The bot check
When you first put the cursor in an email field, or send a form, the page loads Cloudflare Turnstile, which checks that a person, not a script, is signing up. It looks at details such as your IP address and your browser’s user agent (the browser and system you use), and Cloudflare also uses them to improve Turnstile. Cloudflare’s Turnstile Privacy Addendum explains how.
Who sends the emails
SeerShark LLC, 418 Broadway, Ste N, Albany, NY 12207-2922.
Where it’s kept
With Buttondown, the email service SeerShark uses to send these updates.
How long it’s kept
Until you ask for it to be deleted. While you’re subscribed, it’s used to send these updates. If you unsubscribe, or never confirm, it gets no updates. The details that arrive with it, such as the campaign tags and your IP address, are kept with it.
Your choices
Every update email has an unsubscribe link. You can also ask for your email address to be deleted by writing to hello@seershark.com.
What stays out of links
This page never puts your email address in a link, a page address or an analytics event.