All articles
10 min read

Software Project Kickoff Checklist: What to Settle Before Day One

A rolled blueprint, a clipboard with a short checklist, and a rubber stamp with ink pad arranged on a clean drafting table, lit by a small amber desk lamp.

A good software kickoff comes down to five written answers: what problem the project solves, what is in and out of scope, who decides, what could go wrong, and what happens in the first two weeks. If any of the five is missing, the project does not start. It starts searching. The checklist below walks through what to settle before the meeting, what to run in it, and what to send afterward, for a website, app, platform or automation project.

At Ampersand, senior engineers join the project from the first conversation to handover, so the points below are the ones we want settled with every client before a line of code is written.

TL;DR

  • Write the problem and what it costs you in two sentences before you invite anyone. If you cannot, the project is not ready.
  • Fix scope in writing, including what will not be delivered, plus acceptance checks for every part.
  • Name one person who can say yes on each major decision, and give every open item an owner and a decide-by date.
  • Settle data sources, integrations, hosting costs, data protection and code ownership before design, not after.
  • Send a written summary within 24 hours. A kickoff without a written record did not happen.

Why the kickoff decides how the project ends

Most problems that surface in month four were vague in week one. CodeFirst, a UK software firm, traces most failed projects back to something left unclear at the kickoff stage. Logic Grid Studio describes the same pattern when discovery is skipped: scope grows mid-delivery, integrations turn out harder than assumed, and the damage usually shows up three to six months after the start.

That is where mid-project rewrites come from. The requirements were never wrong in a dramatic way. They were never pinned down, so each side built a different picture of the same project.

The Swiss consultancy alerion makes a related point: budget enough time at the start to align guardrails, responsibilities and accountabilities, and delay the start rather than run late for the whole project. A week spent on the checklist is cheaper than a month of rework.

Before the meeting: the pre-kickoff checklist

Work through these items in the days before the call. Most of them can be done in a shared document by the client and the team lead together.

1. The problem, in two sentences

Write what goes wrong today and what it costs the business, in time, money or lost customers. CodeFirst’s test is blunt: if you cannot write it, the project is not ready to start. Start with the problem, not the software. “We need an app” is a solution. “Our team re-enters every order by hand and loses about a day a week” is a problem.

Name the person who pays and the person who decides. They are often the same in a startup and different in a larger company. Flenio, a Swiss project tool provider, lists the sponsor and decision authority as the first things to clarify. For each major decision (scope change, design approval, go-live), name one person who can say yes. “The team” cannot approve anything.

3. Goal, scope and non-goals

Write a measurable goal and a list of what is out of scope. The out-of-scope list matters as much as the scope list: it stops two parties from expecting different deliverables under the same project name. For each part of the scope, add an acceptance check, meaning how you will both tell it is done. “The checkout works” is vague. “A customer can pay by card and TWINT and receives a confirmation email” is testable.

If you want a worked view of turning a fuzzy brief into boundaries and measurable outcomes, this scoping process for setting project boundaries shows the logic in another industry.

4. Budget, including what happens after launch

Agree the build budget and the dates. Then add the running costs: hosting, licences, third-party services and support. CodeFirst recommends putting running costs in the budget from the start, because a project that is affordable to build but not to run is not affordable.

5. Team, roles and absences

List who is on the project, how much of their time is confirmed, and who deputizes. The Swiss project-management site qudits points out that absences are often not entered in calendars early, so holidays and substitution rules belong in the first schedule. In Switzerland, where school holidays and public holidays differ by canton, this is worth checking against a real calendar.

6. Data, access and integrations

List every data source the project needs and who supplies it. List every system it must talk to: shop, CRM, ERP, payment provider, identity login. Logic Grid Studio notes that rate limits, schema inconsistencies and access-provisioning timelines are often not visible in documentation. Ask now who holds the credentials and how long it takes to get them.

7. Data protection and ownership

If the system handles personal data, decide how before the design is settled. Switzerland’s revised Federal Act on Data Protection came into force on 1 September 2023 and gave the Federal Data Protection and Information Commissioner more duties and powers. Raise it at kickoff: what personal data is collected, where it is stored, who processes it. Also settle source-code ownership in the contract, as CodeFirst advises. If your project touches regulated data, check the specifics with your own legal counsel.

8. A short risk list with owners

Five risks with a named owner each beat a long list nobody reads. Typical software risks are delayed access, an unclear data source, a stakeholder who has not agreed, an unknown integration and a fixed external date such as a trade fair or funding deadline. Techstack reports that 61% of project delays could be prevented by identifying risk comprehensively up front. That is a vendor’s figure, so treat it as a pointer, not a law, but the habit is sound.

9. Agenda sent in advance

Send the agenda and any pre-reading before the meeting so people can prepare. alerion stresses this in its guidance on the project start. A one-page problem statement, a rough scope list and the risk list make good pre-reading.

The kickoff meeting itself

Keep the meeting short and decision-focused. A 60 to 90 minute slot is enough for most small and mid-size software projects. Atlassian’s IT kickoff playbook uses 60 to 90 minutes as its frame.

Who should be in the room

The project lead, the people who decide, and the subject-matter experts who know how the work is done today. Everyone else can be informed or pulled in for a single topic. If the client’s sponsor and the team lead give different answers when asked what problem the project solves, fix that first and postpone the rest.

A workable agenda

Block Minutes What you settle
Context and why 5 to 10 The problem, its cost, who benefits
Scope and success criteria 15 to 20 In, out, and acceptance checks tied to numbers or yes/no outcomes
Roles and decision rights 10 One decider per major decision
Milestones and dependencies 15 Dates, what blocks what, who supplies what
Risks and assumptions 10 Top five risks, each with an owner
Working agreements 10 Channels, response times, how decisions are logged
Next steps 5 Owners and dates for the first two weeks

The timings echo the structure of MeetGeek’s 2026 kickoff agenda, adapted for a small team. MeetGeek’s example of a working agreement is concrete: a chat reply within four working hours, email within one working day, decisions logged within 24 hours. Pick your own numbers, but pick them.

Two habits that save projects

First, name a minute-taker before you start. OpenProject’s guide, based on the PM² method, lists this among the standard kickoff steps.

Second, test for real agreement. MeetGeek separates buy-in from consensus: silence is not a yes. Ask “What would make this plan fail?” and wait. Atlassian ends its kickoff with a quick thumb vote, green for confident, yellow for open questions, red for concerns, then agrees how to follow up on the yellows and reds. It takes five minutes and surfaces the doubt that would otherwise appear in month three.

After the meeting: the 24-hour follow-up

Send a shared summary within a day. MeetGeek calls this the highest-leverage thing a project lead can do. It should contain:

  • Scope, with the out-of-scope list
  • Owners for each workstream
  • Milestones with dates
  • A decision log, already started
  • Open items, each with an owner and a decide-by date
  • Calendar invites for recurring check-ins and access to the shared workspace

GoTranscript’s minutes checklist sets a useful bar: one to five goals written as outcomes, at least one measurable success signal, and three to eight immediate actions, each with an owner and due date. Ask everyone to acknowledge the summary in writing. If someone disagrees, you want to hear it in week one.

Adapting the checklist to what you are building

The core items are the same for every project. What changes is where the hidden risk sits.

Project type Extra items to settle at kickoff
Website Who writes and approves content and by when; domain and DNS access; existing URLs that must keep working; languages (German, French, Italian, English); analytics and consent setup
Web or mobile app / MVP The single core user journey; which devices and OS versions; app store accounts and who owns them; what can wait for version two
Platform User roles and permissions; data model owners; scaling expectations; admin and support processes after launch
Automation The current process mapped step by step; volume and exceptions; who handles cases the automation cannot; where the data lives
Integration Systems, API access and rate limits; who holds credentials; what happens when the other side is down
Migration or replatform What data moves and what is archived; a freeze period; redirects; a rollback plan; who verifies the result

For content-driven projects, the usual cause of delay is not engineering. It is text, images and approvals arriving late. Put content deadlines on the same schedule as development milestones, with a named owner.

For automation, write down the exceptions before the happy path. Automating a process nobody has documented only makes the mistakes faster.

Common kickoff mistakes

MeetGeek names three that recur: confusing buy-in with consensus, leaving decisions unassigned, and keeping no written record. Add three more that cause mid-project rewrites:

  • Requirements that live in one person’s head. If the scope is not in a document everyone read in the same version, there are two scopes.
  • Assumptions nobody owns. Every assumption (“the ERP has an API”) needs someone who validates it and a due date.
  • Treating the kickoff as the end of planning. qudits notes that not every detail can be settled beforehand, so documenting assumptions is what lets you handle later changes calmly against the original frame.

Another pitfall sits on the supplier side: staff who change mid-project, or requirements reinterpreted by whoever joined last. Ask who will actually work on your project and whether that person is in the kickoff.

How we handle the start at Ampersand

We are a small Zurich studio, and every project is led end to end by senior engineers. The people you speak to in the first consultation stay through to handover, which is how we avoid rewritten requirements and mid-project staff changes. We aim to leave you independent rather than locked in.

Our offers cover websites, web and mobile apps or MVPs, platforms, AI automation, integrations, migrations and ongoing support. Two plans have published prices: Run & monitor at 750 CHF per month and Guidance at 799 CHF per month. Project pricing for the rest is on our pricing page.

If you want a kickoff that settles scope, risks and ownership before the build begins, start with the offers listed on our pricing page and tell us what you are trying to launch.

FAQ

How long should a software kickoff meeting be?

For a small or mid-size project, 60 to 90 minutes is usually enough, provided the agenda and pre-reading went out beforehand. Larger programs can run two to three hours. If the meeting needs longer because basics are still open, the pre-kickoff work was not finished.

Who needs to attend?

The project lead, the decision-makers and the subject-matter experts who know the current process. Others can be informed afterward through the written summary. The client and the lead should be able to give the same answer to what problem the project solves.

What should we have ready before the meeting?

A two-sentence problem statement, a draft scope with non-goals, a short risk list, a list of integrations and data sources, and a named sponsor. Circulate them with the agenda so the meeting is spent deciding, not reading.

What should happen right after the kickoff?

Within 24 hours, send a shared summary with scope, owners, milestones, a decision log and open items with decide-by dates. Ask for written acknowledgement. Then hold the first recurring check-in within the first week.

Can the same checklist work for an automation or integration project?

Yes. Keep the core items and add the specifics: the mapped process and its exceptions for automation, and API access, rate limits and credential holders for integrations. These are the places where hidden complexity appears most often.

Sources

Talk to us

Have a project this touches on?

A free 10-minute call is the fastest way to find out whether we are the right studio for it.

Book a free 10-min call