Proje vitrini hazırlanıyorPreparing project showcaseПодготавливаем витрину проекта
Skip to main content
Architecture

Work keeps arriving at your practice, but nobody knows where each project’s paperwork stopped.

Rocketly links enquiries from landowners, investors and contractors to a single project record. First-meeting notes, the brief, schematic revision rounds, which permit document is waiting on whom and site-visit notes all sit in the same place.

Where an Architecture Practice Loses Track of Its Work

Enquiries from landowners, investors and contractors arrive separately by phone, email and messaging, so no shared record shows who answered which one.

The brief, the site information and the budget expectation discussed at the first meeting stay in one notebook, and the same facts are gathered again when schematic design starts.

No record says which schematic option you are on, so when the contractual revision limit is passed the additional-fee conversation has nothing to rest on.

Missing permit documents, which authority is waiting for what and who is chasing it stay buried in an email chain, and the file quietly stalls at one step.

Notes and photos from a site visit stay on someone’s phone, and a decision made on site is never written to the contractor, so it is argued about later.

How an Architectural Brief Reaches the Practice

Contractor, Investor and Peer Referrals

Most architectural work arrives through someone who knows you. The call is noted on a record, the introducer goes into the source field, and reports show which network actually brings work.

Email and Corporate Invitations to Bid

Corporate and public-sector invitations arrive by email with a requirements document; the thread and its attachments gather on one project record so it is clear who answered.

Portfolio Site Enquiry Form and Chat

The project enquiry form on your portfolio page turns a visitor into a record along with their site details and expected building type, and live chat joins the same history.

WhatsApp Business and Personal Line

Day-to-day exchanges with landowners, photo sharing and site questions run mostly here; both lines can be connected and the thread stays tied to the project record.

Meta and Google Campaign Forms

Campaign lead-form records land in the CRM with their source, so you can see by source which campaign reached a first meeting.

Competitions, Fairs and Exhibitions

Contacts left from architectural competitions, fairs and exhibitions are imported through CSV or Google Sheets, and each record keeps its event tag.

What Rocketly Records in an Architecture Practice

Collect Project Enquiries in One Inbox

Email, WhatsApp Business and a personal line, the website project form, live chat and ad lead forms — the sources your practice connects appear on one screen. Rocketly supports 12 channel types; the practice decides which ones to open.

Record the First Meeting and the Brief

Plot reference, site area, zoning notes, building type, the room programme and budget expectation live in custom fields. The first meeting syncs with the architect’s Google Calendar, and its summary attaches to the same project record.

Shape the Pipeline Around Architectural Stages

Name your own stages: Enquiry → First Meeting → Brief → Schematic Design → Detailed Design → Permit → Site → Handover. The board shows which project belongs to whom and how long it has been waiting.

Keep the Fee Proposal and Agreement With Their Versions

Gather schematic design, detailed design, permit filing and site-supervision line items into a PDF proposal, share it through a client-specific link, and follow view and approval status from the record.

Make Schematic Revision Rounds Countable

Open each presented option and its feedback as its own round; who asked for what and where the contractual revision limit is reached become readable, and anything beyond it becomes an additional-service line.

Follow the Permit File Document by Document

Open separate tasks for the soil report, structural, mechanical and electrical drawings and the title and zoning papers, so it is clear who holds what and where the file is waiting. Approval timing stays with the authority; Rocketly makes the wait visible.

Document Site Visits With Notes and Photos

The visit is booked into the calendar, and on-site notes, photos and decisions attach to the project record through the media library. Anything to be passed to the contractor opens as a task and is followed until it closes.

AI Reply Drafts and Meeting Summaries

AI drafts replies from your knowledge base of service scope and process, and summarizes long threads and meeting transcripts. It makes no design decision and produces no drawing; the architect approves the content.

Reports by Source and Building Type

With 38 ready-made report types, evaluate with your own data which source reaches a first meeting, which building type reaches a signed agreement and where each project is waiting.

Ready to bring the customer communication you connect into one shared workspace?

Configure your process, team and connected sources at a pace that fits your operation.

What AI Takes On in Architectural Work and What It Never Touches

AI can prepare drafts and summaries from conversation context; your team decides what is shared with customers.

Drafts Replies and Written Notices

Produces drafts about service scope, stage definitions and process questions from your knowledge base; the architect edits and decides whether to send.

Summarizes Meetings and Long Threads

Turns a meeting-bot recording into a transcript and summary and shortens months of client correspondence, so context transfers without rereading.

Helps Tag the Incoming Enquiry

Pulls building-type, scale and client-type hints out of the conversation and proposes a tag; the team confirms or changes it.

Makes No Design, Zoning or Permit Judgement

AI produces no architectural decision, interprets no planning regulation and promises nothing about permit outcomes or approval timing. Those judgements belong to the architect and the relevant authority.

One Building From First Meeting to Site Handover

01 · CONTROLLED HANDOFF

Turning a landowner enquiry into a first meeting

01

A landowner writes through the website project form; the record opens and location, site area and expected building type go into fields.

02

AI drafts a reply from the service-scope knowledge base; the architect edits it and decides whether to send.

03

The first meeting is booked through a shareable link and lands on the architect’s calendar.

04

The meeting summary attaches to the record, and a task opens to gather the title deed and zoning certificate.

05

The record moves to the Brief stage and a responsible architect is assigned.

From the brief to schematic approval

The room programme, use scenario, budget expectation and target handover are written onto the record as the brief.

The fee proposal is built line by line and shared through a client-specific link; on approval the agreement is generated from a template.

Each schematic option presented opens as its own round, and feedback items become a task list.

As the revision limit approaches, the responsible architect is notified, and anything beyond it is prepared as an additional-service line.

Chasing the permit file document by document

Separate tasks open for the soil report and the structural, mechanical and electrical drawings, each naming its author and expected output.

The submission to the authority is noted on the record; when a deficiency notice arrives it attaches to the relevant task with an owner.

The board shows which step the file is waiting at; approval timing stays on the authority’s calendar and the practice tracks only its own step.

Once the permit is issued the record moves to the Site stage and supervision visits are planned as tasks.

Turning a site visit into a decision and a written notice

The visit is booked into the calendar, and photos and notes taken on site are uploaded to the project record.

Points discussed with the contractor and consultants open as tasks with an owner and a due date.

The written notice is drafted, the architect edits it and decides whether to send, and the sent text stays on the record.

Unclosed tasks carry over to the next visit agenda, and the pre-handover snag list runs from the same record.

Automations for Schematic Design, Permits and Site Visits

Use these examples to discuss triggers, owners and review points before configuring your own process.

Routing a New Enquiry to a First Meeting

So a first contact never waits without a named architect

1

Trigger: a new conversation opens on a connected channel or the project form is submitted.

2

Condition: route to the matching architect or partner based on building-type and client-type tags.

3

Action: move the record to First Meeting and prepare a reply draft and a booking link.

4

If no reply goes out within your chosen interval, alert the office manager.

Revision Follow-Up After a Schematic Presentation

So comments are written into a round and rounds stay countable

1

Trigger: the record moves to the Schematic Design stage.

2

Action: open a feedback-collection task and turn incoming requests into round items.

3

Condition: notify the responsible architect as the contractual revision limit approaches.

4

Prepare anything beyond the limit as an additional-service line and keep it as a proposal version.

Permit File and Site Visit Reminders

So a waiting document and a planned visit do not slip

1

Trigger: a permit document task stays open for the interval you chose.

2

Action: open a reminder task for the owner and summarize the waiting step for the office manager.

3

Condition: if the record is at the Site stage, write periodic visit tasks into the calendar.

4

If notes and photos are not uploaded after a visit, send the architect a second reminder.

Connections That Pay Off in an Architecture Practice

Connect native channels directly, or use a webhook for an existing tool — each card makes Rocketly’s role clear.

Email (IMAP/SMTP)

Native connection

Invitations to bid and requirement documents landing on one project record

Google Calendar

Native connection

First meetings, presentations and site visits synced with the architect’s calendar

Google Drive

File / reference link

Drawings, model exports and permit documents reachable from the project record

WhatsApp Business API

Native connection

Client and contractor threads, with site photos, tied to the project record

Google Forms · Webhook connection

Webhook connection

Brief questions turning into a project record along with their answers

Microsoft Teams

Link / manual flow

New enquiry, revision-limit and waiting-document alerts reaching the team channel

The First Steps of Setup in an Architecture Practice

Use these steps to review your process, responsibilities and permissions before going live.

1

Define the practice, the partners and the team

Create project architect, partner and technical office users; use roles to limit who sees which project record, proposal and conversation.

2

Name the project stages

Rename the Enquiry → First Meeting → Brief → Schematic Design → Detailed Design → Permit → Site → Handover flow to match how your practice actually works.

3

Open the site and project custom fields

Define plot reference, site area, zoning note, building type, gross floor area, client type and revision limit; reports are fed from these fields.

4

Prepare proposal, agreement and document-list templates

Turn the fee-item layout, the architectural services agreement and the permit-file document checklist into templates, so every project starts from the same checklist.

5

Connect channels and trial the first flows

Connect email and WhatsApp, add the project enquiry form to your site, and test enquiry routing, revision follow-up and waiting-document reminders on sample records.

6

Set reports and clarify the system boundary

Set up source, building-type and project-stage reports. AutoCAD, Revit, ArchiCAD and your rendering tools keep running in parallel; Rocketly is the enquiry, proposal and process-record layer.

The Rocketly Capacity Behind an Architecture Practice

0

Channel types where project enquiries reach the practice

0

Templates for permit paperwork and site follow-up

0

Report types covering first meetings and the project line

0

Interface languages for overseas clients

The operational examples on this page are not guaranteed outcomes. What is available and how it performs depend on your process, connected sources, permissions and team use.

Architecture Firm CRM and Permits — What Practices Ask

Rocketly is a CRM layer for enquiry flow and client communication: requests from connected channels attach to one project record, the first meeting lands on the calendar, the brief and site information sit in fields, the fee proposal and agreement are stored with their versions, and permit documents and site visits are followed as tasks. It does not replace your drafting or modelling software; it works alongside it as the enquiry, proposal and process-record layer.

No. Rocketly is not a CAD, BIM or visualisation tool; site plans, floor plans, sections, models and images keep being produced in your own tools such as AutoCAD, Revit, ArchiCAD and SketchUp. Rocketly attaches those outputs to the media library and the project record and notes which version went to the client on which date. Large files can be linked through Google Drive and kept reachable from the project record.

You can follow the steps on your own side of the permit file: you open separate tasks for the soil report, the structural, mechanical and electrical drawings and the title and zoning papers, each naming an author, an expected output and an owner. Submissions, deficiency notices and completed steps are written onto the record. Approval timing sits with the municipality and the relevant authorities; Rocketly does not shorten it, it only makes visible which step the file is waiting at and who is chasing it.

You open each presented option as its own round: which alternative was shown on which date, what the client asked for and when the round closed all stay in history. You can define a workflow that notifies the responsible architect as the contractual revision limit approaches. Requests beyond that limit are prepared as an additional-service line and kept as a proposal version, so the extra-fee conversation rests on a record rather than on memory.

Yes. You book the visit from the project record and sync it with the architect’s calendar; photos taken on site, measurement notes and decisions attach to the same record through the media library. Every point raised with the contractor becomes a task with an owner and a due date, the written notice is prepared as a draft and the sent text stays on the record. This is not a GPS field-tracking system: it does not follow location or staff, it documents the output of the visit.

You gather schematic design, detailed design, permit filing and site-supervision items into the quote module and share a PDF with the client through a dedicated link; view and approval status are followed from the project record. An approved proposal links to the agreement template and the invoice flow, stage payments can be scheduled as recurring invoices and payment status is visible on the record. Statutory ledger and tax filing work stays with your accountant.

Yes. You separate projects using custom fields such as building type, client type, plot reference, zoning status and budget band, and build segments and reports from them. If housing, commercial and villa work need different stage names, you can set up boards accordingly. Access is role-based: you limit which user sees which project record, proposal and conversation, and activity history is retained.

The interface runs in 3 languages: Turkish, English and Russian. You run client correspondence in whichever language you choose, note the conversation language and time zone on the project record, and plan first meetings and presentations accordingly. Conversation summaries let the team pick up context without rereading long threads; the practice decides which language proposals, agreements and presentation documents are prepared in.

The free plan has no time limit, no credit card is requested and there is no trial period to run down. You can bulk import your existing client and project list from CSV, Excel, VCF or Google Sheets, mapping name, company, phone, email and custom fields; checking the mapping with a sample file first is recommended. AI features, advanced workflows, the meeting bot and some channel connections sit in paid plans.

Architecture Firm

Follow Projects From Enquiry Through Permit to Site

Keep the first meeting, the brief, the revision round and the document status on one project record.

Best Prices

The Right Plan for Your Business

Monthly

Yearly
2 Months Free

Free

$0

/month

Basic CRM features

Sales Pipeline

Gemini AI support

Email notifications

Starter

$29

$25

/month (Billed yearly)

$58 savings

All Free features

Unified Inbox

Sales Pipeline

Lead Scoring

Excel/CSV Export

💎 MOST POPULAR

Professional

$79

$66

/month (Billed yearly)

$158 savings

All Starter features

Visual Workflow Builder

WhatsApp Personal Integration

All AI engines (Claude, GPT-4, Groq)

Workflow Templates (12+)

✦ BEST VALUE

Business

$199

$166

/month (Billed yearly)

$398 savings

All Professional features

AI Chatbot Agents

Multi-Agent Routing

Knowledge Sources (25)

AI Training Interface

Construction CRM

$950

$792

/month (Billed yearly)

$1900 savings

All Business features

Construction CRM Module

Unit & Block Management

Payment Plans & Installments

Auto Contract Generation

Start using Rocketly today.


Discover the CRM built for your industry.