Objo Client Tool Handoff (Delivery)

Objo Client Tool Handoff (Delivery)

1. 01

   Confirm the client's Objo Studio license status before build sign-off

   Objo Studio is licensed per developer at £8.25 monthly, billed annually, and the license covers desktop, web, and command-line apps in one seat. If the client will maintain the app in-house, they need their own seat; if your agency retains maintenance, keep the build on an agency seat and note the renewal date so a lapsed license does not strand a delivered tool.

2. 02

   Freeze the Objo language version used for the build

   Any version released during the 12-month license window is yours to keep and use forever, so record the exact Objo Studio build number in the handoff pack. That pins the client's compiled executables to a version your team has already tested rather than whatever ships after the license window closes.

3. 03

   Export the compiled artifacts for each target platform

   Objo Studio builds self-contained executables for macOS, Windows, and Linux with no runtime dependency on the host machine, so the client never installs a separate .NET runtime or an Objo Studio license on end-user machines. Package one binary per platform the client actually runs and label each with the build number from the previous step.

4. 04

   Hand over the deployment routine for web targets

   Server-side web apps compile to self-contained executables, but hosting is not included in the license. Document the host the client will use, the port and environment variables the executable expects, and the restart command, then walk the client's IT contact through one deploy on a staging host before go-live.

5. 05

   Transfer the project source and designer screens

   Deliver the Objo project folder containing the drag-and-drop designer layouts, the statically typed Objo source modules, and any AI assistant configuration. If the client's team uses an LLM integration, record which provider is wired in (Ollama, LM Studio, OpenAI, Anthropic, or Gemini) and where the credentials live, so a key rotation does not break the build.

6. 06

   Run a joint debugging session on the client's machine

   Open the project in Objo Studio on the client's workstation, set breakpoints in the debugger, and step through the two workflows the app automates. This confirms the client's staff can reproduce a fault and read variable state without calling your agency for every issue.

7. 07

   Set the support boundary and escalation path

   State in writing what the retainer covers: bug fixes against the frozen build number, new designer screens, or additional platform targets. Priority support comes with the Objo Studio seat, so route vendor-level defects through that channel and keep client-facing fixes on your agency's delivery queue.

8. 08

   Log the license renewal date in the client record

   The £8.25 monthly seat renews annually and gates access to updates. Put the renewal date on the account record with a 30-day reminder, so the agency decides whether to renew for continued updates or hold the client on the version already delivered.