Recruiting
Vacancies, candidate base and a hiring kanban in one place
$49 / month
Project stages, time tracking for architects and fees against costs — in one system instead of spreadsheets
Trusted by architecture firms and design offices






















The day-to-day problems of running projects in an architecture firm — and how if.team brings structure, visibility and control to every stage
In if.team every stage has a budget and the hours already logged against it. When design development has used 70% of its fee at 40% of the work, the project manager sees it this week, not in the final report.

Stages, client approvals and deliverables sit on one Gantt chart with owners and dates. If the client sits on the concept for two weeks, everyone sees which stages move and by how much.

The workload view shows hours planned against hours available per person and per site. Work is moved between projects on the same screen, and the hours logged by stage keep the picture real.

Drawings, specifications, contracts and client comments live inside the project and its stage. A new team member opens the site and sees its whole history; the client approves in one place.

Each project shows fee, hours at the architects’ rates, subcontractor costs and the margin left — updated as hours are logged. The owner sees which sites earn and which only keep people busy.

Emails, Telegram, Viber and WhatsApp messages attach to the client card and the project. Approvals, comments and files stay with the stage they belong to, not in someone’s personal inbox.

Ask which projects lost money and why, who is overloaded next week, how much you earned this quarter. The assistant takes data from your if.team — projects, hours, finances — and answers in a normal chat
Learn more
if.team integrates with the tools your team already uses every day
Discuss integrationsVideo reviews from teams using if.team every day

Financial planning used to be a real pain — endless Excel sheets and nothing automated. With if.team it's simple: automation, bank integration, and reports in just a few clicks.
Andrii Zaikin
Founder & CEO, YEP Accelerator

Oleksandr Pavlishyn
Development Director, event agency

Iryna Siharova
Founder, Content Bar studio

Yevhen Nozhenko
CEO, HiStory DM
Latest product updates and new features.
Choose the plan that fits your team. Prices are per company, and every plan starts with a 7-day free trial.
For small teams
For growing teams
For mid-size teams
For large teams
For scaling companies
For large companies
Full white-glove service
Some capabilities are connected separately, as paid add-ons
Vacancies, candidate base and a hiring kanban in one place
$49 / month
Quotes built from your services catalog with discounts and DOCX or PDF export
$19 / month
Rules that run the routine for you: trigger, condition and action in tasks and projects
$19 / month
Chats from messengers and social networks in one inbox and in the client card
Stages — concept, schematic design, construction documentation, site supervision — run as iterations inside a project with their own deadlines and owners. Progress per stage is visible on the Gantt chart.
Each site is a separate project with its own budget, team, and documentation. The main Gantt chart shows how stages of different sites overlap.
Yes. Dependencies are set between stages: a hard one recalculates dates automatically when the previous stage slips, while a soft one only records the correct sequence.
Files are attached to a specific site or task, and DOCX, XLSX, and PDF files open directly in the system. Folder access is controlled by roles.
Yes. Enquiries and correspondence are stored in the contact or lead profile — added manually, from a connected mailbox, or from messengers — so context is not lost between managers.
The estimate is assembled from items, volumes, and prices inside a quote, then exported to DOCX or PDF using the firm’s template with the client’s details.
Yes. Income, contractor costs, and team hours are linked to the site, so the margin is calculated per project rather than only for the firm as a whole.
Yes. Subcontractors are kept as contacts with a history of work, and their costs are categorised and linked to the specific site.
The workload calendar shows each specialist’s availability by date across all sites, including time off, so new deadlines can be set realistically.
if.team runs an architecture project as a sequence of stages — concept, schematic design, construction documentation, site supervision — with deadlines, owners, hours and money attached to each stage. Unlike a general task manager, it shows the fee against the time already spent, so the firm sees margin per project, not just a list of tasks. Planning, time tracking by stage, documents, client approvals and project finances live in one system.
A system that keeps projects, stages, team workload, time tracking, documents, and finances in one place, so a firm sees budgets, hours, and profit per project without separate spreadsheets. if.team is built as this kind of all-in-one ERP for architecture and design studios.
Yes. Each project has a budget, payments, payroll and other expenses, and a P&L view, so profitability is visible per project and per client.
Trello and Asana manage tasks; they don’t know what a stage, a fee or a billable hour is. In if.team a project carries its budget, the architects’ hours by stage and the resulting profit, plus drawings, contracts and client approvals — so the project manager and the owner look at the same numbers.
Yes. Architects and engineers log hours against tasks and stages, and the system converts them into labor cost using fixed or hourly rates, so planned versus actual time is visible for every stage.
Most teams set up their workspace and start running real projects within a few days. Onboarding support is included throughout the setup process.
An architecture project in if.team is a chain of stages with their own deadlines, owners and budgets. The Gantt chart shows which stage is late and what it blocks; the dashboard shows the fee, the hours already spent and the margin left. Nothing lives in a separate spreadsheet.
In if.team architects log hours against a stage, not against the firm in general. Hourly contracts are billed from these records; fixed-fee projects show where the fee is being eaten. Workload reports use the same hours, so planning and billing never disagree.
In if.team every file sits inside its project and stage: drawings, specifications, contracts, client comments and approvals. A new team member sees the whole history of a site without asking around, and the client gets one place to approve.
A proposal is built from the stages and rates, goes to the client, and on approval becomes the project with its budget. Invoices are issued from the same record. The fee quoted, the hours logged and the money received form one chain — nothing is retyped.
See how if.team helps architecture practices manage projects, drawings, deadlines, and finances in one place.