Feedback ends up spread across a Slack thread, a comment on the file, and an email nobody can find again. The hours it takes to act on it go unrecorded. CraftTime keeps the note on the design itself, logs the time while you work, gives the PM a straight view of who is busy and what is finished, and hands the devs the specs and every version once the design is approved.
No credit card needed · Cancel anytime
Same team, same project, two very different Friday afternoons.
Not made-up testimonials — just the everyday problems that made us build CraftTime in the first place.
The problem
You do the client work yourself, and the admin lands on you at the end of the day. Feedback arrives across email threads and calls you have to piece back together, and by Friday you are guessing at the hours you actually worked.
With CraftTime
Feedback comes in on the design itself, so you act on it where it was left. Your hours are logged as you work and the report is ready at month-end without you reconstructing anything. When you take on a PM, the team view is already there.
The problem
The PM brings you the features they have picked off the roadmap, and the feedback on them arrives in a dozen different ways. Notes get buried, nobody is sure what has already been actioned, and the hours the work really costs vanish into a spreadsheet nobody keeps up.
With CraftTime
Feedback from your PM lands as numbered pins on the design, and the two of you iterate on the same checklist until the design is done. Your PM signs it off, it goes to the devs with the specs and every version attached, and your hours were logged the whole way.
The problem
You work the roadmap, decide which features go in, then hand them to your designers and devs. But your feedback goes out as a wall of text, half of it gets misread, and a round of revisions that should take a day stretches into a week.
With CraftTime
You click straight on the design to pin exactly what needs to change, and you and the designer iterate on one clear, prioritised checklist. When you approve the finished design it goes to the devs with the specs attached, and the team’s tracked hours are there when you report on progress.
They're solid tools, but they were built for engineering teams working through tickets. Design work is visual, so we built something that starts from the design itself. Here's how it differs.
| Capability | CraftTime | Jira | Monday.com |
|---|---|---|---|
| Feedback pinned directly on the design image | |||
| Pins auto-convert to task checklists | |||
| Automatic revision checklist from feedback pins | |||
| Auto-detects design app & starts timer (Figma, PS, AI) | |||
| Built-in time tracking tied to billable hours | Manual add-on | Separate tool | |
| Invoices generated from tracked time | |||
| Client feedback via public link — no login or license | Paid guests | ||
| Client requests arrive by link, then get an owner, queue, priority and answer-by time | |||
| Design asset shown on every board card | |||
| Structured design→dev handoff notes | |||
| Client approval workflow — approve or request changes, no login | Paid guests | ||
| Zero-config onboarding — invite & go | Setup required | Setup required | |
| Per-person sustainable pace tracking & burnout early warning | |||
| Estimate vs actual hours per project | Manual field | Manual field | |
| Purpose-built for design teams (designers + PMs) | Engineering teams | General purpose |
Feature comparison as of July 2026. Based on publicly available information.
A GitHub-style heatmap of your focus time. You'll see your good weeks, notice the slow ones before they become a habit, and keep a streak going if that's what motivates you.
Activity
Daily focus hours · last 16 weeks
142h
48 active days
Nobody writes "exhausted" in a status update. CraftTime learns what a normal week looks like for each person from the hours they track, so when someone has been over it for a few weeks you can see it and have a word with them before it turns into a crash.
Sarah J.
Product Designer
22h so far this week · on pace for 34h · usual week 23h
Third week above their usual hours. Worth a check-in.
Estimate vs actual
Nine short loops through the app, in the order a project actually runs. Watch them play.
Your PM clicks the exact spot that needs changing and drops a pin. That pin becomes a checklist item on the task by itself, so nothing gets retyped into a separate list.
Tasks move across the board as the work actually moves. Each card keeps its design asset, its checklist and its feedback pins attached, so a task is never just a title.
Waiting to start
Start the timer and get on with the work. CraftTime attaches the hours to the project, and nudges you to step away when you've been at it too long.
Put an estimate on a task. The moment the tracked hours pass it, the task flags itself and asks one question: was this the client's extra work, or our own overrun?
Fonts, colours, spacing, asset links. The designer fills in the specs once and marks it ready, and the devs stop chasing anyone for the details.
The reports were being written the whole time you were working. Pull them at month-end and invoice what you actually did instead of what you remember doing.
Send clients one link where they describe what they need. It arrives in your inbox already sorted: someone owns it, it sits in the right queue, and it carries an answer-by time set from its priority. One click turns it into a task on the board with the brief attached.
A shared home for the things your team keeps re-writing: onboarding steps, brand rules, process notes. Every save is kept, so when someone pastes over the whole page you roll it back.
One link shows them the work and asks a single question: happy, or changes needed? Their answer lands back on the board by itself, and you stop chasing replies.
Plans from $6/seat · 7-day free trial · Cancel anytime