Drafting the first pass of a security questionnaire
Reads the questionnaire, finds the matching answers in your policies and earlier replies, and drafts each one in your own words, with a flag on anything it could not find.
This page lists the jobs around the code in a UK software company that Claude can take on, by function and by the size of the company. It is written for founders, CEOs and COOs. Claude does not write your product. It takes the questionnaires, renewals, billing, board numbers and paperwork that surround it, and it helps you build the internal tools you would otherwise rent.
A founder-led company answers its own security questionnaires and chases its own invoices. A scaling one has people for customer success and finance who spend their week joining systems together. An established one has heads of function, a board and procurement teams on the other side of the table. Pick the one closest to yours and the rest of the page follows it, from where the time goes to the calculator.
These are the tasks that land on the founder and the first few hires, grouped by the kind of work they are.
These are the tasks that come round every week in a scaling software company, grouped by the kind of work they are.
These are the tasks that come round every week in an established software company, grouped by the kind of work they are.
This is the point of the whole page. The work in the left column is why customers buy from you and stay. The work in the right column is what has grown up around it, and in most software companies it takes more of the week.
This is the point of the whole page. The work in the left column is why customers buy from you and stay. The work in the right column is what has grown up around it, and in most software companies it takes more of the week.
This is the point of the whole page. The work in the left column is why customers buy from you and stay. The work in the right column is what has grown up around it, and in most software companies it takes more of the week.
The use case for AI is taking away the time that gets spent on the work sitting around the job, and freeing your people up to do the work only a human can do. The work that grows the business, and the work they enjoy the most.
The times are our own estimates for a typical task in a UK software company. Nobody has published measured times for this work, so where a source gives a figure we say who published it. Every use case assumes a business plan whose terms keep your content out of model training. The highlighted use cases either take the most hours or make the biggest difference to the company.
Every questionnaire, certificate and security promise a buyer asks for.
Reads the questionnaire, finds the matching answers in your policies and earlier replies, and drafts each one in your own words, with a flag on anything it could not find.
Takes a question worded in a way you have not seen and finds the answer you gave to the same question under different words, so the replies stay consistent.
Reads every questionnaire you have completed and turns the answers into one library, grouped by topic, with duplicates merged and contradictions listed.
Takes the unanswered questions from a questionnaire and sorts them by who in the company can answer, with the question reworded so that person can reply in a line.
Reads the customer's data processing terms against your standard one and lists each place where they differ, with the clause that matters and the wording you usually offer.
Compares the list of suppliers you use with the sub-processor list you publish, drafts the change notice customers are due, and notes which agreements give the customer a right to object.
Drafts the public page that answers the questions buyers ask first, from your policies and certificates, and flags the lines that no longer match.
Builds the device and cloud service list, the multi-factor coverage and the patch timeline from your exports and drafts the answers. Since April 2026 it asks for MFA on every cloud service.
Checks your risk register, statement of applicability, internal audit notes and management review minutes against each other and lists the gaps an auditor would find.
Reads the full test report and writes a short summary for customers covering scope, date, what was found and what was fixed, leaving out anything that would help an attacker.
Reads the security schedule a customer wants in the contract and compares each requirement with what you do today, line by line.
Redlines, order forms and the dates every contract hides.
Compares the customer's version with your standard agreement and lists every change, grouped by how much it matters, with your usual fallback next to each one.
Turns the deal notes and the agreed price into an order form on your template, checking the term, the price, the users and the renewal date against what was agreed.
Reads every signed contract and pulls out the start date, term, renewal terms, notice period, price rises and termination rights into one register with a calendar of dates that matter.
Lists the customers with terms that differ from your standard, such as a lower liability cap, longer notice, price caps or audit rights, so everyone knows what has been promised.
Takes the outage record and the customer's contract and works out whether a credit is due and how much, quoting the clause it used.
Reads an incoming mutual or one-way confidentiality agreement against your standard and flags term, scope, residual knowledge, the law that applies and anything unusual.
Compares a partner's agreement with your standard terms and lists the differences in exclusivity, pricing, data handling, support duties and termination.
The renewal conversation, the account that went quiet and the review.
Pulls together the contract, usage, support history, open issues and the last few calls into one page before you speak to the customer about renewing.
Combines the renewal calendar with what each account owner has written and the usage trend, and gives a view of each renewal as safe, uncertain or at risk with the reason.
Builds the deck or the notes for a customer review from their usage, support tickets, goals and what you promised last time.
Reads the week's usage, tickets and account notes and writes a short update on each account that moved, with the reason.
Reads the history of an account and writes the note the new owner needs: who the people are, what was promised, what is at risk and what to do first.
Looks across usage, tickets, logins and contact history for accounts that have gone quiet or changed pattern, and ranks them by the value of the contract and the date it renews.
Writes the renewal notice from the contract, with the correct notice wording, the price and any increase explained plainly, and a clear next step for the customer.
Works out the price for an addition so it ends with the existing term, shows the arithmetic, and drafts the order form change.
Takes the call recording or transcript and writes the summary, the actions with owners and the update to the account record, in the format your team uses.
Reads every comment from your satisfaction surveys, cancellation forms and review sites and groups them into themes with quotes and counts.
Reads the account history and the exit call and writes a plain account of why the customer left, what could have been done and when it could have been seen.
Replies, escalations and the help centre that stays out of date.
Reads the ticket and your help articles and past replies, and drafts an answer in your tone that a person checks and sends.
Reads new tickets and sorts them by urgency, topic and account value, and spots the same problem arriving from several customers.
Compares the questions customers ask with your help articles and lists the topics with no article, articles that give the wrong answer and ones that nobody can find.
Turns a solved ticket thread into a help article with a clear title, steps and screenshots to capture, and removes anything specific to the customer.
Turns a long ticket thread into a clear bug report with the steps, the expected and actual result, the account and the logs mentioned, so engineering does not have to ask again.
Reads the week's tickets and writes a summary for product and leadership of the top issues, what is rising, which accounts are affected and what was promised.
Reads each ticket that got a poor rating and writes what went wrong: slow, wrong, unclear or a product problem, with the point in the thread where it turned.
Reads your saved replies and rewrites each one to be clear, short and consistent in tone, flagging the ones that are out of date.
The kick-off, the data import and the customer who has gone silent.
Reads the order form and the sales notes and drafts the welcome email, the kick-off agenda and the list of what you need from the customer.
Turns the goals the customer gave in the sales process into a plan with milestones, owners and the measures you will report back on.
Reads the customer's export before it is loaded and lists what will fail: missing fields, wrong formats, duplicates and values the system does not accept.
Compares each onboarding with its plan and flags the ones that have not moved, who is holding it up and what to send.
Takes your standard training material and rewrites it around the way this customer has configured the product, using their terms and their examples.
Builds the go-live checklist from the plan and the configuration, records who confirmed each item, and drafts the sign-off message to the customer.
The CRM update, the proposal, the tender and the pipeline commentary.
Takes the call notes and writes the CRM update: stage, next step, who was on the call, what they said about budget, timing and competitors.
Reads the pipeline and the deal notes and writes the commentary for the forecast meeting: what moved, what slipped and why, and where the notes do not support the stage.
Writes the first draft of a proposal from the discovery call, the order form template and your case studies, in the customer's own words.
Reads the tender, splits it into questions, and drafts answers from your previous responses, product documentation and case studies, with a flag on anything new.
Reads the prospect's website, filings and news and the notes so far, and writes a short brief so the demo is built around what matters to them.
Writes the follow-up email and the shared plan of next steps from the demo notes, with dates for each side and the questions the buyer raised.
Turns a recorded call with a happy customer into a case study draft with their quotes, the problem and the result, and the questions you still need to ask.
Takes the release notes and writes the customer announcement, the email to the base and the post for your channels, each in a different voice.
Reads the notes on won and lost deals and groups the reasons, the competitors named and the objections that came up, with quotes.
Turns your plain description of how leads should be routed into the rule logic, then tests it against past leads and lists the ones it would have sent somewhere surprising.
Matches each closed deal to the commission plan and the payment terms and shows where the statement differs from what the rules say.
Reads competitors' pricing pages, release notes and reviews and updates your comparison notes, marking what changed and what sales should say about it.
Payouts, failed payments, the month end and the R&D claim.
Matches each payout from the payment provider to the invoices and fees behind it, and lists the ones that do not agree.
Compares closed deals in the CRM with invoices and subscriptions in billing and lists every difference in amount, date, term or customer.
Reads each new or amended contract against your recognition policy and drafts the schedule, flagging terms that could change how the revenue is treated.
Reads the failed payment list and writes a message to each customer that fits their history, the plan they are on and how many times the payment has failed.
Writes the chase for each overdue invoice using the customer's history, the contract terms and, where the contract says so, statutory interest for late business payments.
Reads the management accounts against budget and last month and writes the commentary explaining each variance, asking the owner when it cannot tell.
Reads supplier invoices against the order or contract and flags price rises, renewals you did not approve and duplicate charges.
Checks each sale to a customer outside the UK for the evidence you need: that the customer is in business and where they are, such as a VAT number, and lists the gaps.
Reads the project's tickets, design documents and sprint notes and drafts the description the claim form asks for: the baseline, the advance sought, the uncertainties and how they were resolved.
Takes payroll, supplier invoices and timesheet or estimate data and builds the cost schedule by project, flagging items that do not qualify and costs you have not yet paid.
Takes your assumptions on hiring, pricing, churn and costs and builds the budget model, then updates it each quarter and shows what changed and why.
Builds the cash forecast from invoices due, renewals coming, payroll and supplier payments, and shows which customers' late payment would hurt most.
Reads expense claims and receipts against your policy and flags missing receipts, claims over limits, duplicates and items that need a second approver.
Builds the accruals and prepayments schedule from supplier invoices and contracts and shows what rolls forward from last month.
Reads the customer's question and their billing history and drafts the reply that explains the charge, with the contract term that backs it.
The pack, the update and the one ARR figure everyone can defend.
Pulls the financials, the metrics and each function's update into the pack, checks the figures agree across pages, and drafts the summary paper.
Turns the latest numbers and your notes into the investor update in the same format each time, with last period's figures alongside.
Compares the revenue and retention figures in billing, the CRM and the finance system and lists each place they disagree and the likely reason.
Reads how your reports calculate each metric and writes a plain definition, so everyone who quotes ARR or churn means the same thing.
Reads your pack the way a sceptical non-executive would and lists the questions they are likely to ask, with where the pack does not yet answer them.
Writes the minutes from the recording or notes, lists decisions and actions with owners and dates, and updates the tracker.
Reads an investor's or buyer's request list, finds the document that answers each one, flags the gaps, and drafts the explanations that go with them.
Reads the facility agreement and builds the compliance certificate and the calculations the lender asks for from your accounts.
Takes the annual plan and the board's priorities and drafts goals for each function with the measure and the source of the data for each, then reports progress.
Subject access, the complaints duty and a calendar that keeps moving.
Logs the request, lists the systems to search, drafts the search record and the covering letter, and builds the redaction schedule from what the search found.
Drafts the procedure the law has required since 19 June 2026: an electronic way to complain, an acknowledgement within 30 days and a response without undue delay.
Logs the complaint, drafts the acknowledgement for the 30 days, collects the facts from the systems and drafts the response.
Compares your record of processing with the systems you actually use and lists what is missing, what is out of date and which processing has no lawful basis written down.
Compares your privacy and cookie notices with what you now collect and the suppliers you use and drafts the changes, including for the cookie exemptions in force since February 2026.
Writes up an incident as it unfolds, records what was known when, and drafts the record of the decision on whether to tell the regulator and the people affected.
Reads the feature specification and drafts the impact assessment: what data, why, who can see it, the risks and the measures that reduce them.
Checks the renewal date, your fee tier and the register details, and drafts next year's reminder. The regulator became the Information Commission on 30 September 2026.
Keeps a list of what each director and person with significant control still has to verify and file, and drafts the reminders. Existing directors verify through the confirmation statement.
Compares your headcount, turnover and balance sheet with the thresholds in the law that depend on them and lists what switches on, what is close and what applies from when.
Drafts the fraud risk assessment and the prevention procedures for a company that meets two of the three size tests, covering staff, agents and resellers.
Collects the figures and the supplier information and drafts the statement and the pay gap report from your data, when you reach the turnover or headcount that requires them.
Reads a change in the law or guidance and your current policy and lists the paragraphs that no longer fit, with suggested wording.
Reads new laws, regulator notices and bills going through Parliament and writes a short note on whether each reaches a company like yours, and by when.
Reads your sign-up flow, renewal reminders and cancellation route against the consumer subscription rules, now expected to apply from spring 2027, and lists what to change.
Lists where personal data goes outside the UK, the legal route for each transfer and the date it needs reviewing, including the EU adequacy decision, which runs to December 2031.
Registration, declarations, G-Cloud and the evidence buyers ask for.
Collects the core supplier information, from your latest accounts and your connected people, and keeps it up to date before every tender and award.
Walks through the grounds a buyer can exclude you on and drafts the declaration from what you tell it, with the five year look back set out for each.
Drafts the service description, the pricing document and the security statement for each service from your product documentation, in the format the framework asks for.
Reads what the buyer asks for and lists the evidence you hold: the certificate, its scope and any equivalent controls, with what is missing.
Drafts how each of the NCSC's Cloud Security Principles is met for each service, from your policies and architecture notes.
Drafts the accessibility statement and conformance summary from your audit and lists what you plan to fix, in the form public buyers ask for.
Fills in the data protection schedule from your record of processing: the subject matter, duration, data types, who it concerns, transfers and what happens on exit.
Reads the tender and lists the mandatory requirements, the evidence needed, the deadlines and the contract terms that worry you, with a view on whether you can meet them.
Lists every supplier who would touch the work or the data and checks each against your sub-processor list and the buyer's questions.
Release notes, outage updates and the docs that fall behind.
Reads the changes that shipped and writes release notes in customer language, grouped by what the customer will notice, with anything that needs action called out.
Drafts the status updates in plain language from the engineers' notes, in the same format each time, with what is known, what is not and when the next update is due.
Builds the timeline from the incident channel, the alerts and the tickets, and drafts the review: what happened, the impact, the causes and the actions.
Compares the release changes with your help articles and product docs and lists the pages that now describe something that no longer works that way.
Reads feature requests from tickets, calls and the sales notes, merges the duplicates and lists the customers behind each one with their own words.
Rewrites the internal roadmap for customers and for the sales team, leaving out dates you cannot promise and flagging claims that are not safe to make.
Builds the monthly service report from the incident records and your monitoring, in the format each customer's contract asks for.
Works out which customers use the thing, drafts the notice with the dates the contract requires and writes the migration steps.
Reads all the feedback from a beta programme and groups it into themes, with quotes and who said it, and flags comments that point to a bug rather than an opinion.
Hiring paperwork, the handbook and the records the law now expects.
Writes the job advert and the interview scorecard from your description of the role, in plain language, with the must haves separated from the nice to haves.
Summarises each application against your written scorecard, quoting what the person has said, so the first read is quicker and more even.
Fills the offer letter and the contract from the agreed terms and checks every figure and date against the offer email.
Keeps the record of each check: the date, the document type and the copy, and a diary of follow-up checks for anyone with time limited permission.
Builds the plan for a new starter's first weeks from the role, the team and your standard checklist, with who does what and when.
Reads your handbook and contracts against the dates the Act brings in and lists the paragraphs to change, from day one sick pay to the statement about joining a union due from January 2027.
Drafts the policy, the risk assessment, the training record and the reporting route you would show to prove you took all reasonable steps, including for harassment by customers and partners.
Turns manager notes into clear dated records of performance and conduct, so that a decision at six months is backed by what was said earlier.
Reads the feedback gathered for each person and writes a summary of the themes with quotes, and flags where feedback does not match the rating.
Builds the leaver checklist from the person's role and the systems they used, and lists every account, licence and shared password to remove or hand over.
Reads every free text comment and groups them into themes with counts and quotes, by team where numbers allow, without identifying anyone.
The internal tools and glue you would otherwise pay another vendor for.
Builds a small internal tool that pulls the contract date, the invoice status, the support history and the account notes into one page per customer, in your own accounts.
Builds an internal tool that collects the figures from billing, the accounts and the CRM each month and lays out the first draft of the board pack in your format.
Builds an internal tool that takes feature requests from email, tickets and call notes, tags each one and sends it to the right person, without another subscription.
Reads your card and invoice lines and licence lists and shows what you pay for, who uses it and which subscriptions overlap, so you can decide what to keep.
Builds a scheduled job that pulls key figures from billing, support and the CRM each week and sends a short plain English digest to the leadership team.
Builds a calendar from your contracts, certificates, filings and policies that tells you what is due in the next 90 days and who owns it.
Turns the jobs your people repeat into saved skills in your own words, so the way you do it is written down and anyone can use it the same way.
Builds a small job that moves a figure or a status from one of your systems to another where someone retypes it today, with a log of every run.
Builds an internal page from your policies, processes and pricing rules that answers staff questions, so people stop asking the founder.
Lists everything you have built with Claude, who owns it, what it touches, when it last ran and what would break if a connected system changed.
Clearing what does not need a founder, a CEO or a COO.
Reads the inbox overnight and sorts it into what needs you, what someone else should answer, what can wait and what can be answered with a draft.
Reads the week's calendar and the history with each person and writes a one page brief before each meeting, with what was said last time.
Turns a recording or your notes into a summary, decisions and actions with owners and dates, and sends the actions to each person.
Reads the week's calendar, notes and actions and writes a short review of what got done and what slipped, with a proposal for next week's priorities.
Takes your notes and the week's numbers and writes the update to the team in your voice, so it goes out on time.
Writes up each decision from your notes: what was decided, the options considered, the reason and when to look at it again.
Time is the easy part to count. The other parts are keeping customers, winning work and owning what you build. Each has published evidence behind it, and each has a limit that we state next to it.
Renewals are mostly lost in the quiet gaps: a ticket nobody answered, a health check that ran late, an onboarding that stalled. Claude drafts, summarises and flags, and a person sends. The published evidence supports speed and consistency. It does not put a number on retention.
The detailCloseWe do not claim that Claude raises retention or cuts churn by any percentage, because nobody has published a number we would defend. Gartner found that 64% of 5,728 customers would rather companies did not use AI in customer service. The work here is your people replying faster, and no bot takes their place.
For enterprise buyers the security review is the longest wait after you have been chosen. In a small company the queue ends at the founder or one security lead. Claude drafts first answers from your own policies and past replies, a person with authority signs them off, and the library improves each time.
The detailCloseWe do not claim a share of deals won or a number of days saved for you, because nobody independent has published one. Claude does not certify you or replace Cyber Essentials or ISO 27001. Nothing it writes goes into a questionnaire until a person who knows the system has signed it off.
Software companies buy seats for work that is really internal glue: a renewal view, a board pack, a feedback inbox, a sync between two systems. Claude can build and run these in your own accounts, so you stop adding subscriptions for them and the way you work sits in tools you control.
The detailCloseThis is about internal tools, workflows and the connections between systems. It does not replace your billing, CRM, ticketing or accounting system. We do not claim copyright in raw Claude output, because UK law on that is under government review. Someone has to maintain what is built, and we agree who in writing. Take legal advice on the terms.
Every figure names who published it. Where nobody independent has published one, we leave the number out. Anthropic's customer stories are vendor material and we say so.
Nobody independent has published how many hours a week software companies spend on this work, so put in your own.
Costed at £32 an hour. An hour is costed from that salary plus employer National Insurance and pension, over 1,740 hours. No overhead is added.
This values the hours at what they cost you and nothing more. In a founder-led company the biggest cost is usually the founder's own evenings, which are worth more than the salary you enter here.
This is arithmetic on your own numbers and not a claim about what Claude will do. Put in your annual recurring revenue and the share of it you keep each year before any upsell.
For reference, SaaS Capital's 2025 survey of more than 1,000 private B2B software companies found a median gross retention of 91%.
We do not claim that Claude changes retention. This only shows what each point is worth on the figures you entered. Gross retention is the share of revenue kept from existing customers before any upsell.
Not a bigger company. The same company, with the work on the right hand side of that list mostly gone.
Not a bigger company. The same company, with the work on the right hand side of that list mostly gone.
Not a bigger company. The same company, with the work on the right hand side of that list mostly gone.
Pick one use case from this page. Thirty minutes on a call, no slides, and you keep whatever we build.
Book a call