A Telegram bot for architecture studios
that collects a brief and tracks project status
Not every studio needs a full AI agent on day one. A Telegram bot that collects a project brief against a checklist, lets current clients check a project's status and alerts the team to a new inquiry is often enough to stop the manual back-and-forth, built and live in one to two weeks.
Why architecture studios lose money today
Collecting a project brief for a studio follows the same pattern at almost every firm: a prospective client is asked for site details, references, a rough budget and a timeline, and sends half of it over email, forgets the rest, and someone on staff has to track who sent what and chase the gap manually, often during the same week that firm is also trying to finish a deadline for an active project.
Document collection suffers the same scatter. Site surveys, zoning documents, reference images a client mentions in passing, all arrive through whatever channel was convenient at the moment, email, WhatsApp, a text message, with no single place the studio can check to confirm what has and has not arrived for a given project.
The third gap is visibility for current clients. A client who wants to know whether their permit submission went through or what stage their design is at usually has to email and wait for a reply, which is a small interruption multiplied across every active project the studio is running at once.
A fourth, easy to overlook: a new inquiry that arrives outside business hours sits unseen until someone checks the inbox the next morning, and the studios that respond fastest to a serious inquiry are often the ones that win it, regardless of portfolio quality.
What we build for architecture studios
A Telegram bot with one job done well: collect a project brief against a checklist matched to the project type, residential, commercial, renovation, and let a current client check their project’s status without waiting for a reply. Uploaded documents, site surveys, reference images, permit paperwork, are logged with a timestamp and matched to the project, so the studio can see at a glance what is still missing.
Admins get notified the moment a new brief or document arrives, through a separate admin channel, so a serious inquiry that comes in overnight gets a response the next morning instead of whenever someone happens to check the inbox. Checklists and status stages are editable by your own staff through a simple admin panel or bot commands, no developer needed for the routine updates that come with every new project type the studio takes on.
Typical integrations: Telegram Bot API for the client-facing flow and the admin notification channel, a lightweight database for brief and document tracking, and a project tracker like Monday or Notion, or a Google Sheets export, where your studio wants the data to live alongside active project records.
The bot deliberately does not try to hold a conversation about fees or design. It runs a fixed sequence: here is what we need for your brief, here is what is still missing, here is your project’s current status. That narrower scope keeps the build fast and the running cost close to zero.
The bot also timestamps every stage change a project goes through, brief received, concept sent, permit submitted, so a studio reviewing its own pipeline later has an actual record of how long each phase typically takes, rather than a general sense that projects “usually” move at a certain pace. That record becomes useful the moment a client asks why a project is taking longer than a past one did, since the studio can check rather than guess.
What stays with humans
The bot never estimates a fee, never comments on a design direction, and never confirms a permit or feasibility outcome. A message that reads as a design question, a scope change request, or anything about a disagreement over an existing project gets flagged to an admin rather than answered, since a fixed-flow bot has no business guessing at any of those.
Price and timeline
| Model | Price | What it covers | Timeline |
|---|---|---|---|
| Agency runs it | from $900 | We build, host and maintain the bot; checklist updates included for the first month | 1 to 2 weeks |
| Full control, handover-ready | from $1,530 | Same build, plus full source, hosting handover and a written runbook for your own team | 2 to 3 weeks |
Running cost is close to zero beyond hosting, since the bot runs fixed logic rather than a language model on every message.
Related
Pair this bot with a website for architecture studios for the portfolio-facing side, or step up to the full AI agent for architecture studios once FAQ and fee questions outgrow a fixed flow. The quote and proposal generation automation extends naturally once a brief turns into a real proposal. See the full package breakdown on the development service page, read how a fixed-flow bot with an admin-editable knowledge base holds up in production in the visa centre AI support case study, or get a written plan with a fixed price for your studio.
FAQ
What does a Telegram bot for an architecture studio cost?
A bot with brief intake, document upload and status checks is about $900 to $1,500. Adding an admin panel with CRM export typically moves it toward $1,500 to $4,000. We give the exact number in a written plan after a short brief.
How is this different from the full AI agent package?
This bot runs a fixed flow: collect a brief, upload a document, check a status. It does not hold an open conversation about fees or portfolio matching. The [AI agent for architecture studios](/solutions/ai-agent-for-architecture-studios/) adds that FAQ and qualification layer handled by a language model.
Can prospective clients use it without installing anything new?
Yes, it runs inside Telegram, which is already common for this kind of professional-service intake. There is no separate app to install.
Who updates the intake checklist?
You, through an admin bot or a simple panel we build in, no developer needed for routine updates. We only get involved again if the intake logic itself changes.
Can a current client check their project's status without calling?
Yes, the status check flow pulls the current stage from a tracker you update, so a client gets an answer instantly without interrupting a team member who is mid-design.