Contractor

Podcast 2 — In conversation

Speaker A: I have been offered a choice at work: I can stay as a permanent employee or move to a contractor arrangement. The day rate looks very attractive but I am not sure I fully understand the difference.

Speaker B: That is a genuinely significant decision and the financial comparison is more complex than it looks. As an employee, you get holiday pay, sick pay, pension contributions, and employment protections. As a contractor, you get a higher gross rate, but you are responsible for paying your own national insurance, your own pension if you want one, and you have no entitlement to holiday pay or sick pay from the client. You also have no unfair dismissal rights after a contract ends.

Speaker A: So the day rate needs to compensate for all of that?

Speaker B: Exactly. A commonly used rule of thumb is that a contractor day rate should be roughly equivalent to an employee salary divided by two hundred to account for working days in a year, multiplied by a premium of around one point four to one point six to cover benefits, downtime between contracts, and your additional tax costs. If you are being offered a rate that does not clear that bar, the contractor arrangement may not be as attractive as it first appears.

Speaker A: What about IR35? I keep hearing that term but I am not entirely clear what it means in practice.

Speaker B: IR35 is UK tax legislation designed to catch contractors who are, in the eyes of HMRC, effectively employees but working through a limited company to pay less tax. If your engagement is assessed as inside IR35, you will be taxed broadly as an employee, losing most of the tax advantage of contracting. The key tests are control, can the client tell you how to do the work; substitution, could you send someone else to do the work; and mutuality of obligation, does the client have to offer you work and are you obliged to accept it. Genuine contractors should be able to substitute, should direct their own methods, and should face no obligation to accept extended work.

Speaker A: Is contractor the same as freelancer? I tend to use the words interchangeably.

Speaker B: Related but not identical. Freelancer typically implies someone who works for multiple clients concurrently or in rapid succession, often on smaller projects or creative work. Contractor more often implies a single client engagement over a defined period, usually through a contract with a set duration. A software contractor might be engaged on a six-month assignment with one company, working almost full time for them. A freelancer might handle five different clients in the same period. Both work under contracts for services, but the working patterns and the scale of engagement differ.

Speaker A: And subcontractor? I see that used in construction mostly.

Speaker B: A subcontractor is a contractor engaged not by the end client but by another contractor. The main contractor on a building project might engage a subcontractor for the electrical work. The subcontractor has a contract with the main contractor, not with the building owner. The responsibilities and liabilities flow upward through the contractual chain. In technology, the same structure appears when a staffing agency places a contractor: the agency has a contract with the client, the contractor has a contract with the agency, and the contractor is effectively a subcontractor to the agency.

Speaker A: So the word contractor always implies a contract, but the nature of who is party to that contract varies significantly.

Speaker B: That is the key insight. Contractor is a relational word: it describes someone who performs work under a defined contractual obligation. Understanding who holds that contract, and with whom, determines most of the legal and financial implications that follow.

Podcast 3 — Prompt engineering

Speaker B: Contractor is a precise and immediately useful word in software development prompts because entire HR and workforce management platforms are built specifically to distinguish between employees and contractors and to handle the different rules that apply to each.

Speaker A: So using contractor explicitly in a prompt ensures the model builds the right data model and the right business logic from the start?

Speaker B: Exactly. If you just say user or worker, the model makes assumptions. Contractor is specific and triggers contractor-appropriate logic. First prompt, a contractor onboarding portal:

Speaker B: Build a contractor onboarding portal in Next.js. When a new contractor is added to the system, the portal must collect: company registration number (for limited company contractors), IR35 status (inside or outside), agreed day rate, contract start and end dates, notice period, and right-to-work documents. Store each contractor in a contractors table separate from the employees table. Show an onboarding checklist and mark each step complete as documents are uploaded.

Speaker B: Separating contractors from employees in the data model is correct architecture. Mixing them into a single workers table produces a schema that handles neither correctly. The IR35 field and company registration number are contractor-specific data points that the prompt correctly identifies.

Speaker A: The checklist pattern is practical. What is the second prompt?

Speaker B: A timesheet and invoicing system for contractors:

Speaker B: Build a Node.js timesheet API for contractors. Each contractor logs daily hours against a specific contract engagement. At the end of each week the system calculates billable amount as hours multiplied by the contractor day rate divided by eight. Generate a PDF invoice for each contractor using their registered company details, the client purchase order number, and the weekly timesheet summary. Store timesheets in a contractor_timesheets table linked to the contracts table by contract_id.

Speaker B: Day rate divided by eight converts the daily rate to an hourly rate correctly. Using the contractor table for registered company details rather than personal employee data is the right relationship. The contract_id link means all timesheets trace to a specific engagement, which is essential for auditing.

Speaker A: Third prompt?

Speaker B: An IR35 compliance dashboard:

Speaker B: Build a React IR35 compliance dashboard for an HR manager. For each active contractor engagement, display: contractor name, limited company name, IR35 status, contract end date, a risk score based on whether the contractor passes or fails the control, substitution, and mutuality tests (each stored as a boolean in the contractor_ir35_assessments table), and a renewal alert if the contract end date is within thirty days. Colour-code: green for outside IR35 with low risk, amber for borderline, red for inside IR35.

Speaker B: The three boolean fields map directly to the legal test criteria. The risk score derived from them gives the HR manager an actionable signal without requiring legal expertise for every row. The thirty-day renewal alert is operationally important because an expired contractor contract creates a legal gap.

Speaker A: Encoding the legal tests as booleans is a very clean approach. Fourth prompt?

Speaker B: A full workforce platform with both employees and contractors:

Speaker B: Build a Django workforce management platform for a technology firm that employs both permanent employees and contractors. The system must use a polymorphic worker model: all workers share a common profile, but employees have a salary, holiday entitlement, and pension contribution rate, while contractors have a day rate, IR35 status, contract end date, and invoicing company name. The dashboard must show headcount split by employment type, upcoming contractor contract renewals, and total monthly workforce cost calculated correctly for each type.

Speaker B: Polymorphic worker model is the right architectural pattern here. A shared base profile for common fields, separate submodels for type-specific data. The cost calculation difference, salary plus employer NI for employees versus day rate times working days for contractors, is a real business requirement that the word contractor in the prompt correctly flags.

Speaker A: The monthly cost calculation being type-aware is what actually matters to the finance team. Last prompt?

Speaker B: Create a contractor management module for an existing HR SaaS platform. The module must allow clients to invite contractors via email, generate a contractor agreement PDF pre-filled with the agreed terms, track contractor engagement history across multiple contracts with the same contractor, flag contractors whose total engagement with one client exceeds two years (a potential IR35 risk indicator), and export a contractor register as a CSV for audit purposes.

Speaker A: The two-year flag is genuinely useful. Prolonged engagement with a single client is one of the indicators HMRC considers in IR35 assessments.

Speaker B: And that is exactly the kind of domain-specific logic that only surfaces when you use the word contractor in a prompt. Generic workforce or user language would never trigger that consideration. The word carries the legal and operational context with it, and that context flows directly into better, more accurate, and more commercially useful software.