Working with us

How working with Codefield actually works.

Sign once. Then every engagement is a one-page document. Here's what that looks like.

The two documents

One MSA, many SOWs.

Master Services Agreement

Signed once per client. It holds what never changes: confidentiality, assignment of intellectual property on payment, the liability cap, payment terms, data protection, governing law, and what happens if you want to hire one of our people directly.

Statement of Work

One page per person and mode: who, the mode (Flex, Part-time or Full-time), the hours a month, the hourly rate, the SLA if any, start date, expected duration and notice. Fewer hours is an amendment; another person or a different mode is a new SOW. Never a new contract.

Draft · for legal review

Statement of Work

SOW-[YYYY]-[NNN]

Issued under the Master Services Agreement dated [date]. Where this SOW and the MSA conflict, the MSA prevails.

Client: [Client legal name]
Provider: Codefield Tech
Client contact: [Name, role, email]
Codefield contact: [Name, role, email]
Start date: [date]
Expected duration: [n] months, indicative

1. What we’re doing

[Two to four sentences: the outcome the Client wants and where this engagement fits.]

2. Person, mode and hours

Role	Engineer	Mode	Hours / month	Overlap (Client time)	Rate
Senior Engineer	[Name]	Part-time	[80] minimum	10:00–13:00 [TZ], Mon–Thu	£[x]

One mode per SOW. Flex: up to [n] hours a month, billed whether used or not. Part-time: [n] hours a month reserved and billed whether used or not; hours above it at £[x]. Full-time: [40] hours a week in the Client’s working day.

3. SLA

☐ No SLA. Requests are handled on a best-efforts basis within working hours.

☐ SLA: [service levels agreed for this engagement]. Adds £[10] to every hour billed under this SOW, whether or not a request comes in. Requests are worked within these hours.

4. Billing

Hourly, invoiced monthly in arrears against the timesheet visible in the client portal. Payment terms as agreed in the MSA; pay by bank transfer or in the portal. Monthly cap: [none / £x]. Expenses: none unless pre-approved in writing.

5. Changing or ending this SOW

Notice to change hours or mode, or to end: [n] [days / weeks], either party, in writing. Minimum term: [none / n months]. A change of hours is a signed amendment; another person or a different mode is a new SOW. No new MSA is needed.

6. What the Client owns and receives

All code, documentation and configuration produced under this SOW are assigned to the Client on payment. Work happens in the Client’s repositories, cloud and tooling accounts from day one. On completion or termination, Codefield delivers a written hand-over within [five] working days as part of the engagement.

7. Assumptions and dependencies

[Access to repositories, environments and people by the start date; a product owner available for decisions within one working day.]

The defaults

What is fixed, and what is agreed with you.

Hourly, invoiced monthlyAgainst a timesheet you can see at any time, so no invoice is a surprise.Fixed

Four hours a month, the smallest engagementIt keeps small, continuous engagements possible without a retainer.Fixed

Part-time monthly minimumThe hours reserved for you each month, billed whether used or not. Set in each Part-time SOW.Agreed per client or SOW

IP assigned to you on paymentYou are paying for the work; the result is yours.Fixed

Accounts in your name from day oneRepositories, cloud and tooling are yours, so nothing needs migrating when we leave.Fixed

Hand-over includedA written hand-over closes every engagement. It is part of the work, not an extra.Fixed

Discovery as a fixed block of hoursQuoted up front, so you know the cost before we start.Fixed

Payment termsAgreed with you in the MSA. Invoices can be paid by bank transfer or directly in the client portal.Agreed per client or SOW

Notice period and minimum termSet in each Statement of Work, so they match the shape of the engagement rather than a one-size rule.Agreed per client or SOW

SLAOptional, on any mode: one fixed add-on to every hour billed. What it covers is defined in your Statement of Work.Agreed per client or SOW

The rate card

Three roles, three modes, one SLA add-on.

Every invoice can be reconstructed from the rate card and the timesheet. The figures below are illustrative: each project is priced on what it needs, and your own rates are set in the proposal after the first conversation.

Roles × modes

Illustrative — priced per project

Add an SLA

Role	FlexBest rate	Part-timeMid rate	Full-timeHighest rate
EngineerSenior developer: backend, frontend, mobile, integration, cloud.	from £50 / hour	from £60 / hour	from £65 / hour
Architect / LeadSolution and enterprise architecture, project leadership.	Rate per engagementEach case is different.	Rate per engagementEach case is different.	Rate per engagementEach case is different.
Fractional CTOTechnical leadership, a fixed number of hours a month.	Rate per engagementEach case is different.	Rate per engagementEach case is different.	Rate per engagementEach case is different.

* Illustrative rates. We do not publish a price list. Every project is priced on what it actually needs — the people, the seniority, the mode and the duration — and your proposal states the rate for each person before anything starts.

Sign once. One page per engagement after that.

Ask us for the draft MSA and a sample SOW before the call, or start with the call and read them afterwards.

Book a free 30-minute call How we charge →

Who you contract with

Codefield Tech.

One global entity. Governing law and payment terms are set in the MSA; registered details appear on every document.

Hiring our people

You're welcome to. Just ask us first.

If you hire, or engage directly, an engineer who worked with you through Codefield Tech — during the engagement or within 12 months after it ends — a one-off conversion fee of 20% of their first-year base salary applies. On an £80,000 salary, that is £16,000: in line with what a recruiter charges for an introduction, and you will already know the person can do the job.

What you own

The code, the documentation, the accounts.

All code, documentation and configuration we produce is yours on payment.
We work in your repositories, cloud and tooling accounts from the first day.
Every engagement ends with a written hand-over.
When development moves into support, you choose: keep us, take it in-house, or bring in someone else. No lock-in.

What we don't do

Four promises.

We don't place junior developers and call them senior.
We don't take fixed-price bids on work we haven't scoped in discovery.
We don't hold your code, accounts or knowledge hostage.
We don't add recruitment or placement margins to our hours.

Confidentiality, data and liability

The short version.

We treat everything we see in your systems as confidential, during and after the engagement.
We follow your access and security policies and use only the accounts you provide.
Where we process personal data on your behalf, the MSA includes the data-processing terms the applicable law requires.
Liability is capped as set out in the MSA; neither party is liable for indirect or consequential loss.

A sample SOW and a plain-English summary of the MSA will be available here once the documents have been through legal review. Until then, ask and we will send the drafts.

Start here

Start with a conversation.

Thirty minutes, free, no pitch deck. Tell us where the complexity is and we'll tell you honestly whether we're the right people to help.

Book your 30-minute call Or email [email protected]

30 minutes: One call, at a time that suits you
Free: No obligation, no proposal unless you want one
A founding engineer: No sales team on the other end