





MOCO is strong on the commercial side: proposals, invoicing, controlling, budget tracking. What it lacks is a tool for operational project work: tasks, timelines, Kanban boards, team collaboration. Creative teams fall back on other tools when project management doesn't fit, and that costs you data. awork fills this gap: intuitive enough that creative teams actually use it, and structured enough that MOCO gets complete time data.
Clear split. MOCO handles everything commercial: proposal calculation, budget tracking, controlling, invoicing. awork handles project work: tasks, capacity planning, time tracking, client collaboration. The integration connects both worlds: projects start in MOCO, time entries flow back automatically, across the entire project lifecycle.
MOCO passes project number, name, deadline, client, project members, and service items. The budget in MOCO is converted into planned hours for awork (budget ÷ hourly rate). awork passes all tracked time back automatically, including changes to duration and notes. Absences from MOCO also flow into awork automatically, so capacity planning stays accurate.
The project starts with a defined hour budget in awork, calculated from the MOCO proposal. Once time is tracked, it flows directly back to MOCO. Budget consumption is visible there at any point, without manual reconciliation. MOCO always knows where a project stands because awork continuously transfers the hours.
A one-time process, usually quick. You create an API key in MOCO and set up three custom fields: awork project link, sync toggle, and project template selector. Users are matched via email addresses. The awork team guides you through setup and clarifies preferences like absence sync and time tracking start. After that, synchronisation runs automatically.
Yes, active accounts with awork and MOCO are required. awork can be tested for free. As official integration partners, awork and MOCO can offer individual terms – just reach out.