Productivity & Workflows
Reclaim vs. Motion: Decide What You Want an AI Calendar to Reschedule
Current Reclaim 2.0 and Motion documentation supports different scheduling choices. A complete conflict calendar, revised allocation, and two purchasing records separate task sessions from flexible focus time and recurring-meeting controls.
Choose Motion when the work you want automatically rearranged is a list of individual tasks with durations, dependencies, and deadlines. Shortlist Reclaim when you want flexible focus blocks, routines, and recurring meetings to adapt around your calendar. Reclaim 2.0 changes an important comparison: tasks supply recommendations inside protected work time rather than automatically becoming separate calendar events. List the tasks, focus blocks, and meetings that may move before comparing the subscription.
This LandOffer.ai comparison uses official documentation and publicly rendered prices checked October 27, 2026. No calendar was connected, account created, meeting moved, or subscription purchased. The conflict calendar and completed purchasing records below are authored fictional exercises. Their arithmetic is independently checked; neither scheduling engine was run.

Compare the current workflow, including Reclaim 2.0
Reclaim’s current Tasks overview explicitly describes its 2.0 workflow. It brings tasks together and recommends relevant work during Focus Time or other blocks. Assigning a filtered task list to an Agent changes the recommended work, not that Agent’s scheduling rules. The guide identifies users who signed up after May 2026 as already using 2.0.
An older guide explaining how every task automatically receives its own calendar allocation describes a different experience. Confirm your actual version before carrying those instructions into a purchase decision. In 2.0, you can ask Chat for task work blocks and review the proposed calendar changes in Preview Mode. That is different from assuming every newly imported task will generate a dedicated event automatically.
Reclaim’s Focus Time documentation describes a weekly goal, daily limits, minimum block length, and scheduling hours. It also distinguishes general focus capacity from recurring activities handled by Habits. Protecting two hours for work does not establish which deliverable will finish during those hours.
Motion’s scheduling documentation describes a task-centered system using availability, duration, deadlines, priority, and chunking. Its Pro AI pricing package includes projects, tasks, a calendar, and a task planner. This supports a different buying requirement: representing an estimated deliverable as scheduled task sessions. It does not prove that the estimate is accurate or that a task will be completed on time.
Define the work before choosing either product. “Find time for analysis” can mean protecting a general work block, assigning a particular analysis task, or moving the meeting preventing that work. Naming the object prevents a task-planning decision from silently becoming permission to change a meeting.
Set the boundary between a fixed event and a flexible object
Reclaim’s 2.0 priority guide says ordinary calendar events are Critical by default. Lowering a non-Reclaim event’s priority can expose it to a higher-priority Scheduling Link; it does not let every Habit or Smart Meeting overbook it. A broad claim that Reclaim freely moves all existing appointments would misstate that distinction.
For recurring internal meetings, its Smart Meeting Agent adds specific rules. The organizer can set minimum lead time, locking, allowed hours, and an automatic-rescheduling policy. None leaves automatic movement off; Conservative allows one reschedule per day; Moderate allows three and is the default described in the current 2.0 guide; Aggressive allows five. These are limits on movement, not promises about meeting quality.
The same guide lets the organizer retain an unresolved conflict or remove an occurrence when no alternative fits. Those choices have different consequences. Retaining a conflict leaves a decision visible; removal does not mean the discussion became unnecessary. Manually moving an occurrence locks it against further automatic rescheduling unless unlocked.
Motion’s Task Scheduling FAQ supplies another consequential boundary: a hard deadline can schedule a task outside its normal assigned hours. That is product behavior, not permission from an employer or colleague to work late. Keep a genuine deadline visible while resolving scope or capacity with its owner. Do not shorten an estimate merely to make the calendar appear feasible.
In either product, keep genuine busy commitments in the availability calculation. A customer appointment, leave, or required lunch break does not become expendable because an optimizer needs room. Calendar access is also separate from organizational authority to change someone else’s meeting.
Worked calendar: decide what can move before scheduling
Consider fictional analyst Inez and meeting organizer Omar. Both work in an approved 09:00–17:00 window on November 10, 2026, expressed here in UTC. Their employer has not approved either application. Their hypothetical desktop workflow uses Google Calendar; no provider integration or device permission was tested.
Inez has a fixed customer session from 10:00–11:00, protected lunch from 12:00–13:00, and a fixed review from 15:00–16:00. She also has a recurring internal planning meeting from 11:00–11:30. Its participants permit movement, but only after an organizer checks everyone’s availability. For the initial calculation, its current half hour remains occupied.
The remaining windows are 09:00–10:00, 11:30–12:00, 13:00–15:00, and 16:00–17:00. Together they provide 270 minutes. Inez needs 150 minutes for an analysis memo in meaningful sessions of at least 30 minutes, a 30-minute administrative routine, and a desired 60-minute general focus block. These consume 240 minutes, leaving 30 minutes uncommitted. The general focus block is additional capacity, not a second count of the memo.
| Calendar object | Permitted movement in this fictional brief | Reclaim mapping | Motion mapping |
|---|---|---|---|
| Customer session and fixed review | Keep the appointments and their Busy status | Ordinary calendar events remain protected by default | Existing busy commitments constrain task availability |
| Lunch | Keep 12:00–13:00 unavailable | Use a genuine protected commitment; do not infer every Habit is immovable | Preserve the busy event in conflict checking |
| Internal planning meeting | Organizer may seek a mutually available replacement; no unilateral cancellation | Evaluate a Smart Meeting with explicit movement rules | Do not treat automatic task movement as equivalent authority to move the meeting |
| Analysis memo, 150 minutes | Split only into useful sessions of at least 30 minutes | Recommend the task during protected work blocks, or review proposed task work time | Enter the duration, deadline, schedule, and meaningful chunk size |
| Administrative routine, 30 minutes | Move within the allowed work window | A Habit is a documented recurring-work fit | A recurring task can represent the work, with its own scheduling behavior |
| General focus, 60 minutes | Flexible capacity; not another promised deliverable | Focus Time matches the general-capacity requirement | Do not assume a general calendar block supplies task completion evidence |
One completed manual plan places memo work at 09:00–10:00 and 13:00–14:30, administration at 11:30–12:00, and general focus at 16:00–17:00. The interval 14:30–15:00 remains free. This is a feasible paper allocation under the stated assumptions, not a screenshot or output from either product.
Now a genuine customer follow-up occupies 13:00–14:00. The free capacity falls from 270 to 210 minutes. The desired 240 minutes exceed it by 30, even though a calendar may still show several gaps. The completed revision keeps the 150-minute memo and 30-minute routine but reduces general focus to 30 minutes for this day. Memo sessions become 09:00–10:00, 14:00–15:00, and 16:00–16:30; administration stays 11:30–12:00; general focus becomes 16:30–17:00.
All 210 minutes are now allocated. No slack remains for overrun, another task, or an unlisted break. The revision is acceptable only because the example’s focus goal is negotiable; it does not establish that real work can safely fill every minute. A longer honest memo estimate would require another decision.

Two completed choices from the same conflict
Personal-deliverable brief. Inez wants the memo’s duration and sessions represented explicitly, with dependencies and a visible deadline. She is willing to use a task-centered workspace, but has no authority to move Omar’s meeting. Her completed documentation-based choice is to shortlist Motion Pro AI for a controlled evaluation. The stated per-task scheduling matches her requirement; speed and completion remain unmeasured.
Her proposed task record includes 150 minutes, a 30-minute minimum useful session, the correct work schedule, and the actual deadline. She records the revised allocation above as an independent reference. The hard-deadline exception remains a review item: an evening placement would trigger a discussion about the remaining work rather than an assumption that overtime is available.
Reclaim remains viable if she instead prefers protected work capacity with recommendations about what to do inside it. That is a different operating preference, not evidence that Reclaim lacks tasks. Her note rejects an obsolete comparison claiming that both current products automatically create a separate event for every task in the same way.
Recurring-meeting brief. Omar’s problem is different: repeatedly coordinating internal meetings around genuine calendar conflicts while preserving focus capacity. He wants limits on how frequently an occurrence can move and a visible unresolved conflict when no replacement fits. He keeps the same Inez calendar and task estimates; he does not pretend the new customer hour disappeared.
His completed shortlist is Reclaim, subject to confirming the required plan and attendee access. The proposed meeting rule is Conservative movement, a minimum lead time agreed with participants, and retention of an unresolved conflict when no slot fits. Omar must agree the lead-time value with participants before enabling the proposed policy. The note explicitly rejects changing the meeting simply to manufacture Inez’s task capacity without checking the others.
Motion’s task scheduling still addresses Inez’s deliverable. Its presence in the comparison does not establish the same recurring-meeting movement policy. Omar’s decision is based on the documented control he needs, with account-level behavior and recipient experience still untested.
Price the selected scope and the AI usage separately
The public Reclaim pricing page rendered Starter at $12 per seat monthly and $10 per seat per month with Yearly selected. Starter listed 10 AI Agents per seat and up to 10 seats. Lite was free, with five Agents and a shorter scheduling range. These are public display observations, not a checkout or a promise that any particular configuration fits Lite.
The Motion pricing page rendered Pro AI at $29 per seat with Pay monthly selected and $19 with Pay annually selected. Business AI displayed $49 and $29 respectively. Pro included 7,500 monthly credits per seat; Business included 15,000. The additional-credit rates changed with the interval selection: Pro showed 39 cents per 100 monthly and 25 cents annually; Business showed 33 and 19 cents. Do not combine an annual base rate with an assumed monthly credit price.
At those displayed dollar rates, one Starter seat totals $144 across twelve monthly payments versus $120 using the yearly equivalent. One Motion Pro seat totals $348 across twelve monthly payments versus $228 using the annual equivalent. The $108 annual-base difference compares these named offers; it does not compare equal products or incorporate taxes, discounts, add-ons, or unmeasured productivity.
Three hypothetical paid Reclaim Starter seats would have a $36 monthly base or $360 annual base. Three Motion Pro seats would have an $87 monthly base or $684 annual base. Those calculations do not prove that every meeting attendee needs a paid seat or that these are complete organizational quotes. Reclaim’s fetched page contained attendee-user and older promotion blocks absent from the rendered current cards; no expired promotion or unverified attendee charge is counted as current entitlement here.
Agent allowances, chat credits, and scheduled minutes are different units. These allowances do not establish how many useful decisions a particular balance will produce; the evaluation must check actual usage separately from calendar fit. Keep the existing calendar when fixed events and manual task planning already meet the need. Before connecting either tool, identify the calendar objects it may change, the people affected, and the exact plan and billing interval. Return to LandOffer.ai for related workplace guides; the next decision here is a bounded evaluation against your calendar rules, not permission to rearrange every commitment.
Sources and Further Reading
- Reclaim 2.0 Tasks overview
- Reclaim Focus Time Agent
- Reclaim 2.0 priorities
- Reclaim Smart Meeting Agent
- Motion auto-scheduling
- Motion Task Scheduling FAQ
- Reclaim pricing and Motion pricing — public interval selections inspected October 27, 2026; no checkout or account evaluation.


