In a five-person development company, the founder may also be the architect, salesperson and project manager. A new enquiry arrives in the morning, a client needs an estimate for extra work by lunch, and the afternoon goes on explaining why the support allowance has run out. Coding waits until evening.
Small IT service providers face the same problem: user support, systems maintenance and new implementations run alongside each other. Each job may be small, but remembering every agreement and next step becomes a job of its own.
Studio OS helps organise the operations around this client work. Its business agents help process enquiries, prepare proposals and follow project progress. You set the direction, clarify the important agreements and review proposals that need a decision.
Turn an enquiry into a clear scope and proposal
“We need a self-service portal” is not yet a development task. Before promising a price, you need to know who will use it, which integrations it needs and what the first version must do. Studio's sales agent Kairi helps keep client communication and proposal preparation together. Your team confirms technical feasibility and scope.
Once the work is agreed, project agent Madis helps follow tasks, progress and blockers. Shared proposals, documents, work status and invoices can be available through the client portal, giving the customer a place to find information about their order.
Extra work deserves an agreement too. If a client requests another integration halfway through development, record its scope and the effect on price and delivery. Studio provides the client and project context; the development team estimates the change and the client accepts the proposal.
Business agents keep client work moving
Kairi helps organise sales conversations and proposals. Madis follows delivery tasks, missing information and project progress. Liisa helps prepare invoicing. Sven coordinates company-level work and brings decisions to the people responsible for them.
These agents work with the client and project records in Studio. A request passed to a colleague carries its brief and relevant context, so the next step has an owner and a place in the ongoing work.
Keep the brief, decisions and delivery together
Your developers use their chosen development tools. Studio keeps track of the client agreement, project context, tasks and business follow-up around their work.
When a proposed business action needs approval, Studio brings it to the responsible person. The team keeps code review, testing and release decisions in its development process. Madis can follow missing information and delivery commitments in the project.
Start with one client project: keep its scope, owner, next action and approval decisions in Studio, then check whether less work gets lost between conversations.
Wemply helps show where people's time goes
Using AI leaves plenty of human work to account for. Analysis, client meetings, code review, testing and support still take the team's time. If those hours go unrecorded, it is difficult to know which projects are worthwhile.
Wemply supports manual time entries and timers, including project-based tracking. It also covers work schedules, holidays, absences and payroll. For a small IT company, this provides a basis for understanding both recorded hours and team availability.
Wemply time tracking and workforce management features
Studio's HR agent Piret has a read connector for Wemply employees, schedules, absences, holiday balances, working time and wage reports. Adoption requires Wemply access and validating the queries against the company's actual data. The current connector does not create or change time entries in Wemply; automatically linking project hours to Studio invoices needs separate implementation.
An example: a small improvement to a client's portal
Imagine a four-person team whose existing client wants a CSV export in their portal. A workflow using Studio to coordinate the client work could look like this:
- Enquiry and scope. Studio holds the client request and proposal. A developer clarifies the export fields, access rules and acceptance criteria. The client agrees to the scope and price.
- Development. The team lead gives a developer a bounded task with its acceptance criteria. The developer prepares the code change and tests using the team’s chosen tools.
- Review. A person reviews the change, checks data visibility and confirms the tests pass. Release follows the team's agreed process.
- Time. People record analysis, development and review time in Wemply. Software and AI usage costs are tracked separately from human hours.
- Handover. The client-facing project status is updated in Studio and billing is prepared according to the agreement. The lead compares the completed work with the original estimate.
This illustrates a possible division of work. Automatic movement of project hours from Wemply into Studio invoices requires separate implementation.
Look at human time and AI costs together
AI usage costs and Wemply timesheets answer different questions. One records software usage; the other records people’s time. Understanding a project’s delivery cost also requires other direct costs, such as test environments or purchased services.
For an hourly engagement, agree with the client what you will bill. For a fixed-price job, actual time helps reveal whether the estimate's assumptions held up. The amount of AI-generated code or the duration of an agent run does not itself represent billable human hours.
One client and one recurring type of work are enough for a first pilot. Measure how long proposals take, how quickly a task reaches a verified result and whether everything needed for billing is available at month-end. Use those answers to decide what to expand next.
Studio keeps client agreements, business tasks and next steps together. Developers own the technical delivery. Wemply helps account for people’s time. Clear responsibilities give a small team more time to build solutions.