What ShipItFam does
Each part below solves a problem people run into when they build things with AI. Every section starts with that problem.
First, which one are you?
This page explains things differently for each. You can switch later.
Showing the page for people with an idea.
A team of AI specialists
One AI chat doing everything loses track of what it was doing, and guesses when it isn’t sure.
- SpecWhat and why
- PlanYou approve
- BuildSmall steps
- CheckSecurity and tests
- ShipYou approve
It writes down what you want first.
A product owner turns your request into a short spec, and only asks what it can’t work out itself.
You see a plan before anything is built.
An architect splits the work into small steps. You approve the plan, or say in a sentence what to change.
A second AI checks the plan.
Fammy, our parrot, looks for gaps and risks before the plan reaches you.
A specialist for each step.
Front-end, back-end, devops and QA each take the steps that fit them. Edit these roles, or add your own.
It asks instead of guessing.
When a step needs a decision only you can make, it stops and asks you.
Nothing risky without your yes.
Risky actions wait for you, and a security check runs before anything goes live.
An app for your decisions
When the AI needs you, you might be on a train or asleep. Answering shouldn’t need a desk.
One list of what needs you.
Questions, plans to approve and finished work, from all your projects, with a notification when something arrives.
Answer by tapping, typing or speaking.
Want something different? Say it in a sentence and it redoes that part.
A preview before anything goes live.
Every finished job comes with a preview you can open on your phone.
Choose how technical it talks.
From “just tell me it works” to “show me the diff”.
Use it from Claude or ChatGPT.
Start jobs and answer its questions from the AI assistant you already use.
It remembers your project
Other AI tools forget your project when the chat ends, so you explain it all over again.
A project notebook.
Every answer you give and everything it learns is written down in the Treasure map, and read before every step. You answer once.
One brief for the whole job.
The spec and the plan travel with the work, so the fifth step knows why the first one happened.
A record of every change.
The Ship log lists what changed and when. Come back after a month and nothing is a mystery.
Shared across projects.
Something learned in one project is known in your other projects too.
Work that runs without you
Some work is the same every week. Some can just wait in a queue until it’s done.
Routines.
Tasks that run on a schedule: every morning, every Monday, every month. A weekly sales report, for example.
Autopilot.
Give it a list of tasks, the hours it may work and a spending limit. It does them one by one.
Starters.
Ready-made projects with the first task already written, like a weekly report or a landing page.
Your board as the to-do list.
Cards on your Trello or Gitea board become tasks. Finished ones move to Done by themselves.
Works with what you already use
Most AI tools want you to move your code, your tasks and your apps into them.
Hundreds of apps.
It can read and update Gmail, Slack, HubSpot, Notion, Stripe and hundreds more.
Your code stays yours.
Your project lives in a GitHub or Gitea repository you own. No repository yet? Start from a ready-made project.
Your own tools and skills.
Connect your own systems, or teach it a new skill from a link. We check new skills before they run.
A database when it needs one.
Postgres, MySQL, Redis or MongoDB, set up for the project.
Publishing with an undo.
Put it live on a shipitfam.com address. Every publish goes on a timeline, and one tap undoes it.
Runs where you want.
On your own computer (Free), in our cloud while your computer is off (Builder), or on a dedicated server (Fleet).
For teams
Add a second person to a plain AI setup and edits clash, and nobody knows who asked for what.
Invites.
Each teammate gets their own list, with only what needs them.
Several computers, one project.
Everyone’s AI team works on the same project, and it warns you before two people change the same file.
Roles you can edit.
Product owner, architect, front-end, back-end, devops and QA. Change what each one does, or add your own.
The Kraken: AI assistants that can ask each other
More and more teams write code with AI assistants. When yours needs something only a teammate knows, it either guesses or someone gets interrupted. The Kraken is a small program each teammate runs on their computer. Your AI asks theirs, and it answers from the code they wrote.
- 11:40 pmGeorgi’s AI asks
Why does the refund job retry 3 times?
- Same minuteMira’s Kraken reads her code
Mira is asleep. Her laptop is on.
- 11:41 pmIt answers
Keep 3. The payment provider blocks fast repeats.
- From then onSaved for the team
The answer goes into the project notebook for everyone.
Only reads.
It never changes a file or runs a command, and only looks at the projects you allow.
Asks you when unsure.
You get a notification with the question and a drafted answer. Send it as it is, or write your own.
Real work needs your yes.
If someone asks for a task (“can you check my changes?”), you see exactly what was asked and by whom. Yes runs it on your computer. No does nothing.
Spends what you allow.
It uses your own Claude account, with a spending limit for each answer. Joining takes one command from your team invite.
Soon
What we’re building next.
Jira and Monday boards.
Tickets there become tasks too.
Bitbucket and GitLab.
Keep your code there instead of GitHub or Gitea.
Tasks from Slack or Discord.
Start a task by writing it in a chat message.
Webhooks.
Your own systems get told when a task finishes or needs you.
Cost per task.
See what each task cost to run.
Your own domain.
Publish on your own address, not only a shipitfam.com one.
One-click setups.
Common app connections, set up in one tap.
Want to try it on your project?
Join the waitlist. We’ll let you in as soon as there’s a spot.