Skip to main content

Contracting Work: Delivering as a Contracting Developer

Basic

Applies to: Lieber engineers working as contracting developers on customer engagements · Time to learn: 20 min reading + the first-week checklist

A contracting developer is an external contractor who delivers work to a Lieber customer. You write the code, run the workshops, and present the results, but the customer experiences all of it as Lieber. Your behaviour in the first meeting, in the status update, and in the pull request is the company's reputation with that customer.

TL;DR
  • You represent Lieber in front of the customer. The customer judges the company by how you communicate and deliver.
  • Be polite, precise, and concrete. Write things down. Confirm what was agreed.
  • The contract is your protection. Follow its scope, use its change process, and keep to its boundaries.
  • You own what you deliver, whether you wrote it by hand or with an AI agent, and you own what you missed.
  • Set expectations early, and when the work points to a real follow-on need, raise it openly and let the customer decide.

Who you are on the engagement​

A contracting developer works inside the customer's world under a Lieber contract. The customer may not know the difference between Lieber staff, a partner, and a contractor, and that does not matter to them. Each message you send, each demo you run, and each deadline you hit or miss becomes evidence of what Lieber is like to work with.

This has two consequences:

  • Your standard is the company's standard. A careless email reflects on Lieber, and so does a careful one.
  • Your job is more than the code. You are also the person who keeps stakeholders informed, makes decisions visible, and keeps the work inside what was agreed.

The rest of this section turns that into five working principles.

The five principles​

  1. Polite, precise, concrete. Be courteous, but say exactly what you did, what you will do, by when, and what you need from the customer. Replace "soon" and "should be fine" with dates, numbers, and named owners.
  2. The contract is your protection. Follow it. The statement of work (SOW), the acceptance criteria, and the change process define what you are there to deliver. Work outside them goes through a change request, not through a favour.
  3. You own what you deliver, AI or not, and what you missed. An agent can write code quickly, but the result is still yours. Review it, verify it, and say so plainly when something is late or wrong.
  4. Clear scope and boundaries. Name what is in scope, what is not, and who decides when the two blur. Say no politely and offer a path, such as a change request or a later phase.
  5. Manage expectations and spot real opportunities. At a PoC, be clear about what it proves and what it does not. When the evidence points to a real next step, make the case for it, and only when the customer's need is real.

Pages in this section​

PageWhat you'll learnRead it when
Customer CommunicationWriting and speaking to customers so they stay informed: stakeholders, status updates, written recapsBefore your kickoff meeting, and every week after
Contracts, Scope, and BoundariesHow the SOW, change requests, and collaboration scope protect you, and how to set boundariesBefore you write or accept any new task
AccountabilityOwning your deliverables, reviewing AI-assisted output, and handling a missed deadlineWhen you hand over work, or when something slips
PoC Expectations → MVPSetting the right expectations at a PoC and making the case for an MVP or productificationWhen a PoC is nearing its end, or its results are being discussed
Upsell OpportunitiesRecognising real follow-on needs and raising them in an ethical wayWhen you see a need the current scope does not cover

Engagement lifecycle​

Each stage has a page that applies to it. The diagram shows where to look next.

StageMain questionPage to apply
KickoffWhat exactly are we delivering, and to whom?Contracts, Scope, and Boundaries, Customer Communication
DeliveryIs the work on track, and is it still in scope?Customer Communication, Accountability
Demo and reviewDoes the output meet the acceptance criteria?PoC Expectations → MVP if it is a PoC, Accountability
Close and handoverWhat is delivered, what is not, and who owns what now?Accountability
Follow-onIs there a real next need, and how do we raise it?Upsell Opportunities, PoC Expectations → MVP

First week on a new engagement​

Work through this list before you write production code. Each item takes minutes to hours, and each one prevents a common problem later.

  • Read the SOW, including the scope, exclusions, milestones, and payment terms that affect delivery.
  • Read the acceptance criteria. If they are missing or vague, ask for them in writing now.
  • Confirm the stakeholders: who sponsors the work, who approves it, who uses it, and who to call when blocked.
  • Confirm the channels: where you post status, where files live, and how urgent issues reach people.
  • Confirm access: repositories, environments, data, accounts, and VPN, with the owner of each.
  • Agree the status cadence: how often, in what format, and to whom. Put it in the calendar.
  • Write the kickoff recap: goals, scope, stakeholders, milestones, open questions, and next steps. Send it and ask for corrections.
  • List the assumptions you are making and get each one confirmed or flagged as a risk.
  • Set up the feedback loop for the project: build, test, and lint commands that run locally and in CI. See How We Build.
  • Agree the change-request route for anything outside the SOW, before the first request arrives.

AI-assisted delivery​

Agents are part of how Lieber delivers, and they make it faster to produce code, documents, and test data. The same accountability applies to all of it. Set the project up so the agent can verify its own work, keep the customer's rules in the repository, and review every diff as if you wrote it yourself. The practical setup is covered in AI-Native Engineering.

For the shared engineering standards that every delivery uses, including the definition of done, see How We Build.

Sources​

  • Manifesto for Agile Software Development, the four value statements, including "Customer collaboration over contract negotiation" and "Responding to change over following a plan": https://agilemanifesto.org/

The manifesto ranks collaboration above negotiation. It does not say contracts are unimportant. Use the SOW and change process to keep collaboration clear, not to replace it.