For your workData science

Data science project management for work that rarely runs straight.

Each question gets a card, each experiment its dataset, metric and result, and each model release the same checks. Claude writes the weekly update, and a fleet takes the tests and pipeline chores overnight.

A month of Premium free, no cardAgents never take a seat

Sound familiar?

What slows a data team down.

Nobody remembers which run won, or why we dropped the other one.

With ProjectifyEach experiment is a task with dataset version, metric and result fields. The decision is recorded with the alternatives you ruled out.

People want a date for research that has no date.

With ProjectifyClaude writes the weekly update from the board: what was tried, what was learned and what comes next, so the question gets an answer even when the date cannot.

The engineering around the model never gets done.

With ProjectifyLeave tests, refactors and docs ready on the board. The fleet takes them overnight in their own worktrees and opens pull requests.
What Claude does for data science

Fewer chores around the model, more time with the data.

Takes the pipeline chores

Unit tests, schema checks, refactors and docstrings: fleet workers on your machine take them overnight and open pull requests that never merge on their own.

SLT-12: 14 tests added, one failing on null tenure.

Keeps experiments comparable

Fields for dataset, metric, baseline and result turn the board into a log you can sort. Table shows every run side by side.

Baseline AUC 0.71, boosted 0.78 on the March holdout.

Reads the papers and the dictionary

Papers, data dictionaries and old analyses are read when you add them, so anyone can ask what a column means or what was tried last year.

Data dictionary: tenure is months since first paid invoice.

Releases a model the same way

Freeze the data, evaluate, second review, model card, shadow run, switch. The workflow stops at each check for a person.

Churn v3: evaluation done, metrics wait for Lena’s check.
Your board, shaped for data science

Start from a sentence. Keep what fits.

Say what the project is for and Claude drafts it: the statuses, fields and views below, ready to rename, switch off or add to.

Statuses

QuestionExploringExperimentingPeer reviewIn productionParked

Fields

Dataset versionMetricBaselineResultNotebook or PROwner

Views

BoardTableOutlineTimelineDashboard
  1. Freeze the training data
  2. Evaluation on the holdout
  3. Second reviewer checks the metrics (a person checks)
  4. Model card from the report
  5. Shadow run against the current model
  6. Owner approves the switch (a person checks)

Model release, as a workflow. The clay steps stop for a person. How workflows work

Questions

Before the team tries it.

Does it fit machine learning project management?

Yes. Custom fields hold the dataset, metric and result for each run, Table compares them, and decisions keep the options you ruled out.

Can Claude see our data?

Claude sees the board, the files you add and, for the fleet, the repo on your own machine. Your warehouse stays where it is, and Enterprise can run on your own servers.

Does it replace our experiment tracker?

No. Keep the tool that logs your runs and link each run in a field. Projectify holds the questions, decisions and work around them.

Does the fleet need a repo?

Yes. The fleet runs in Claude Code on your machine and works on code, opening pull requests in GitHub. Analysis tasks without code are run chat by chat.

Let Claude take the chores around the model.

A month of Premium free, no card, and your first question on a board today.