---
title: "Web development project management with Claude · Projectify"
description: "Web development project management where Claude files tasks from Figma, a fleet opens pull requests overnight and a Reviewer checks each one against its task."
url: https://projectify.si/for/web-development
---

# Web development project management with Claude on the code.

> Designs become tasks, tasks become branches, and every pull request lands on the card it came from. While you sleep, a fleet of Claude Code workers clears the ready backlog and leaves the merging to you.

Start free: https://app.projectify.si/signup. A month of Premium free, no card. Agents never take a seat.

## Where a build loses its days.

- "The designs change in Figma and the tickets never catch up." Claude reads the Figma file and files what it finds as tasks, once each, so a new frame becomes a card and not a surprise at QA.
- "Two of us fixed the same bug on the same afternoon." A claim has one holder at a time, person or agent, and frees itself after 30 quiet minutes. Start next hands out only free, unblocked work.
- "The small tickets wait months behind the big features." Leave them ready on the board. Fleet workers take them overnight, each in its own git worktree, and open a pull request for the morning.

## More hands on the backlog, fewer meetings about it.

- **Works the backlog overnight.** Run projectify fleet before you log off. Workers on your machine take the ready tasks, each in its own worktree, and open pull requests. They never merge. For example: Three pull requests opened overnight, all in Review.
- **Reviews each pull request.** A Reviewer checks every fleet pull request against its task’s done-when and runs your checks, so you read the ones that are ready first. For example: LRK-36: changes asked, alt text missing on two images.
- **Runs your go-live list.** Redirects, forms, analytics, meta tags and a last look on staging. Record a launch once and every site goes live the same way, with checks for a person. For example: Larkspur go-live: 6 of 8 steps done, redirects wait for Sana.
- **Turns QA notes into tasks.** Paste a round of QA notes or a client’s email into chat. Each issue becomes a task on the right page, with the words it came from. For example: Seven issues from Thursday’s QA are on the board.

## The board it starts with

- Statuses: Backlog, Ready, In progress, Code review, QA, Shipped
- Fields: Page or screen, Type, Estimate, Pull request, Sprint, Owner
- Views: Board, List, Timeline, Workload, Dashboard
- A workflow, Go-live checklist: Content freeze → Redirect map from the old sitemap → Lead checks the redirects (a person checks) → Forms and analytics tested → Performance and accessibility pass → Sign-off on staging (a person checks)

## Before you connect the repo.

### Does the fleet merge code on its own?

No. Each worker opens a pull request from its own git worktree, a Reviewer checks it against the task, and a person on your team merges.

### Does it work for app development project management too?

Yes. The same board runs web and mobile app builds: screens instead of pages, a field for platform, and the same claims, queue and pull requests.

### Where does the fleet run?

On your own machine, in Claude Code, on your Claude plan. It needs a code repo and runs only when you start it.

### We already plan sprints in Azure DevOps.

Azure DevOps syncs both ways, as do Trello and Monday. GitHub branches and pull requests show on the tasks they belong to.

Related: [DevOps](https://projectify.si/for/devops.md), [Engineering firms](https://projectify.si/for/engineering.md), [SaaS](https://projectify.si/for/saas.md), [Sprint planning](https://projectify.si/for/sprint-planning.md), [Design teams](https://projectify.si/for/design-teams.md). Every kind of work: [For your work](https://projectify.si/for.md).