Skip to content

Software house template

Who this is for: an owner who builds apps or websites for clients and wants a team of agents to run the path from the first chat to the warranty — with every price, quotation and start of work still decided by you.

Every client request is a ticket in Bakulai: a Project with a stage, requirement Tasks under it, and Issues for support after delivery. The engineering work itself lives in GitHub issues, each linked to its Task.

Stage Who What happens
Discovery Product Manager Talks with the customer, asks the critical questions, writes requirements with acceptance criteria.
Requirements Product Manager → you The PRD is complete; you review and approve it.
Quotation You You send the quotation (the product manager can prepare the draft).
Development You → Lead Developer Only after the down payment is received on the Sales Order. The lead developer splits each requirement into GitHub issues.
QA QA Each task is tested against its acceptance criteria.
UAT Product Manager The customer tries it; their approval is recorded word for word.
Handover → Warranty → Done You Final invoice, warranty period, then closed.

The customer only ever talks to customer service and the product team. Engineering never writes to a customer: a developer’s question goes to the product manager, who asks the customer in plain language.

Once the product manager opens a ticket, that customer’s chat belongs to the ticket: every later message on the customer-service number goes straight to the product manager, in one conversation, instead of being routed again. When the ticket is closed (or after 14 quiet days), the chat returns to customer service.

  1. In Bakulai (ERP), choose the business type Software House / IT Agency. It shows Projects and Support and creates the project and ticket types.

  2. In Bakulai Agent, open Settings → Office → Set up from a template… and pick Software house. The first team is a Product Manager, a Lead Developer and a Developer; QA, a Business Analyst, a UX designer and a Finance agent follow when your plan has room. Say yes to WhatsApp to get the customer-service agent.

  3. Give the Lead Developer, Developer and QA a GitHub token (click the agent → Settings → GitHub). Use a fine-grained token limited to the client repositories, with Issues and Pull requests read/write (the Developer also needs Contents read/write to push code). The Lead Developer and QA work GitHub only through GitHub’s own tool connection — they have no terminal, and merging or changing repository settings is not available to them.

  4. On the customer-service agent, open Routing and switch it on. The rows App / new project (→ Product) and App bug report (→ customer service, which logs a support ticket) are already filled in.

  5. On each project, set Code Repository (owner/name) so the lead developer knows where to open the issues.

  • Approving the PRD, sending the quotation, and moving a project to Development — Bakulai refuses Development until the Sales Order is submitted and a down payment is recorded (tick Start Without Down Payment for internal work).
  • Moving to UAT, Handover (needs the customer’s recorded acceptance) and Warranty (needs the warranty end date).
  • Agents can only move a project from Discovery to Requirements, from Development to QA, or back to Requirements when something is unclear.
✦ Ask your agent

Things you can say to an agent in Bakulai Agent:

“set up my office as a software house”“which stage is the Budi project in?”“why can't the project move to development yet?”
  • “what would the software-house template give me?”runs directly
  • “(the product manager) open a ticket for this customer's app”runs directlycoming soon
  • “(customer service) log the customer's bug report”runs directlycoming soon
  • Ticket tools in a customer conversation never take a project name from the conversation: the chat itself decides which project is meant.
  • Support tickets are matched to the customer by their WhatsApp number; Telegram and email reports are logged without a customer.
  • New requests after the requirements are agreed become Change Requests — quoted separately.
  • A message the product team writes to a customer from the office (a developer’s question, the weekly progress note) waits for you under the customer-service agent → Routing → Waiting for your approval, and you get a note on your phone. Messages inside the customer’s own conversation go out directly.
  • Customer words (a bug report, the PRD) never reach an agent that has a terminal through the hourly sync.
  • A customer’s messages still go to customer service — the product manager has not opened a ticket yet, or it was closed. You can hand a held chat back under the customer-service agent → Routing → Chats held by a project ticket.
  • The project will not move to Development — link the Sales Order on the project, submit it, and record the down payment.

The first-office wizard · One number per room