What to bring to a kickoff

The best kickoffs aren’t slide decks. They’re honest answers.

You don’t need a perfect brief. You don’t need to know the difference between a framework and a CMS. You don’t need mood boards unless you like mood boards. A few clear answers save weeks of guessing — and guessing is how projects get expensive in the wrong places.

Here’s what actually helps when we sit down (or get on a call) to start something real with Sciocore. John Martin and our team have run kickoffs for sites, apps, hosting cleanups, and multimedia packages for a long time. The pattern is familiar: the projects that start with truth finish cleaner than the ones that start with theater.

This article is long on purpose. Kickoff is where scope, budget, and ownership either get honest — or get postponed until they’re expensive. Read it once, assemble the kit at the end, and you’ll already be ahead of most first meetings.

Who this is for

Not “everyone.” Not “the general public.” Who, specifically, should recognize themselves on the site or in the app?

Homeowners in a service area. Shoppers comparing two local options on a phone at lunch. Office managers buying for a team. Fans of a product. Patients who are nervous and need calm clarity. Parents booking on a break between jobs. Contractors looking up a supplier while sitting in a truck.

If you serve more than one audience, say which one pays the bills. Secondary audiences can get a page. Primary audiences get the homepage. Trying to speak to everyone equally usually means speaking to no one clearly — and then wondering why the contact form stays quiet.

A useful trick: name a real person. “Maria, who googles emergency plumber at 9 p.m.” beats “homeowners 25–54.” We can still do demographics later. Start with a face.

What should someone do

Every useful digital thing has a job. Call. Book. Buy. Apply. Download. Show up. Email. Walk in with less confusion. Request an estimate. Watch a commercial and remember the name.

If the answer is “learn about us,” dig one level deeper. Learn about you… so they do what? Awareness without a next step is how sites become museums. Museums are lovely. Most businesses need a phone that rings.

Pick a primary action. Secondary actions can exist. Ten equal buttons means no button matters. If you’re split between “call” and “book online,” say which one you can actually handle this quarter. A booking button that dumps into a full calendar or an unanswered inbox is worse than a clear phone number.

What already exists

Bring the leftovers. Old site. Logo files (real files, not a screenshot from Facebook). Brand colors if you have them. Photos from jobs, the shop floor, the team. A competitor you quietly admire. A site you hate and can explain why. An old commercial. A menu PDF that somehow still runs the business. A Google Business profile that’s more current than the website — tell us; that’s useful data.

Also bring the ugly truths: the booking process that only works by phone, the Facebook page that is somehow more current than the website, the domain that renews under an old employee’s email, the store plugin that never quite worked on phones, the “temporary” homepage banner from 2022.

We can work with partial piles. We cannot invent assets you don’t have without either creating them or choosing placeholders on purpose. Placeholders are fine when everyone knows they’re temporary. Pretend-final stock photos of handshakes are how brands get blurry.

What’s off-limits

Constraints are gifts. “We can’t change the logo this year.” “We have to keep this URL.” “No chat widgets.” “The owner hates stock photos of handshakes.” “We will not be on TikTok.” “Mail has to stay on Microsoft 365.” “The franchise desk has to approve colors.”

Say the nos early. Designing into a silent veto wastes everyone’s week. A constraint spoken in minute ten of kickoff is kindness. A constraint spoken after “final” design is a tax.

If you’re not sure whether something is off-limits, say that too. “We might need to keep this booking tool” is enough for us to ask the next question instead of assuming a greenfield fantasy.

Budget and timing in plain numbers

You don’t need a spreadsheet novel. You need a range and a date that matter.

“We need something live before the fair in October.” “We can spend X this quarter and more next.” “We’re exploring — no hard deadline.” Those sentences change the plan. A fantasy budget with a fantasy date produces a fantasy timeline.

If you’re not ready to share numbers on day one, say what you’re trying to protect: cash flow, a launch event, a partner’s patience, a seasonal rush. We’ll map options instead of pretending one quote fits every life. Phased work — stabilize, then extend, then polish — is often the honest path. Stretching a small budget across a giant wishlist is how resentment gets scheduled.

We’re used to real budgets. That doesn’t mean everything is cheap. It means we won’t design a project that requires a second mortgage when an 80% relief plan this quarter would get you breathing again.

Examples you like (and don’t)

Three links beat thirty. For each, one sentence: “I like how clear the phone number is.” “I hate the popup.” “This feels like our tone.” “Their video sounds like a real shop, not a bank.” Taste is easier to discuss with examples than with adjectives like modern or clean — those words mean opposite things to different people.

Include offline references if they matter: a packaging card, a truck wrap, a menu, a radio spot, a storefront. Brand is bigger than the browser. If your best brand moment is the way the counter staff greets people, say that. We’ll try not to build a site that contradicts the room.

If you only have “I know it when I see it,” we’ll still talk — but bring at least two examples of what you don’t want. Negative space helps. Endless open taste with no edges is how projects wander.

Logins and ownership

If we’re touching anything live, bring access — or bring the person who has it. Domain, hosting, email, analytics, social pixels, the old WordPress admin, the store, the booking tool, the registrar where the name actually lives (not where you think it lives).

If you don’t have access, that becomes agenda item one. Half-projects fail on missing keys more often than on missing inspiration. We’ve watched weeks disappear over a domain locked to an old employee’s personal email. That’s not a design problem. It’s an ownership problem — and it has to be solved before the fun work starts.

Ideally the business owns the registrar and hosting accounts. We can manage the technical side. We should not be the only humans who can renew yourname.com. Same with admin mailboxes on renewal notices. Two people who can get in beats one hero and a future crisis.

Bring renewal emails if that’s all you’ve got. Screenshots of error messages help. A messy spreadsheet beats a perfect story.

Decision makers

Who can say yes? Who can say no later and unwind two weeks of work? If a partner, spouse, board, or franchise desk gets a vote, we’d rather meet them early than redesign after “final.”

One primary contact for day-to-day questions keeps momentum. Committees can review milestones. They shouldn’t edit pixels by group text. Unlimited stakeholders with equal veto power is how a homepage becomes five arguments stacked vertically.

If someone important hates change, say so. Fear of change is normal. Surprising that person with a finished rebuild is optional pain.

Content reality check

Who writes words? Who approves words? Do you have service descriptions, bios, FAQs, legal lines, pricing rules? Do photos exist that aren’t screenshots?

If content will be late, say so. We’ll structure the build so design and development aren’t frozen waiting for a paragraph about shipping policy. Empty pages at launch help nobody — plan for what’s truly ready. A strong phase one with honest “coming soon” beats a launch full of placeholder Latin and wrong hours.

Short, clear, accurate beats long and vague. If writing isn’t your thing, say that. We’ll help you say it in your voice — not brochure English. We’re not here to sand you into sounding like every other business within twenty miles.

Technical and operational truths that save weeks

Kickoff goes better when a few unglamorous facts are on the table:

• Where does email live today, and who breaks if DNS changes?
• Is there a store, booking tool, or CRM that must stay?
• Any compliance or franchise rules we should not discover in week six?
• Seasonal rushes when you cannot afford downtime
• Whether the current site has SEO value worth protecting with redirects
• Whether anyone has ever restored a backup on purpose

You don’t need perfect answers. “I’m not sure” is useful. “I think Bob set that up in 2019” is useful. We’ll turn fuzzy into a checklist.

What we bring to kickoff

Questions. Constraints turned into a path. A sense of whether this is repair, rebuild, or something new. Honest talk about hosting and domains if that’s in play. A sketch of phases if the whole wish list doesn’t fit the first budget. Plain language about multimedia if a commercial or product video is part of the story. A willingness to say when a template is enough — and when it’s a trap.

We explain without making you learn our jargon first. If something’s a bad fit, we’d rather say that early than win a project we’ll both regret. Sciocore is built for people who want to work directly with someone who can see the whole picture — design, code, hosting, multimedia, practical AI when it earns its keep — and who will still answer when the site hiccups at an inconvenient hour.

Forty-plus years taught us that availability beats theater. Kickoff is where we start earning that, not where we perform a pitch deck.

Repair, rebuild, or new — deciding without drama

Not every kickoff is a greenfield dream. Sometimes you inherited a mess. Sometimes you launched last year and the site is already drifting. Sometimes you need hosting quiet before you need a new homepage.

We’ll help you choose with practical questions. Can we make urgent customer-facing problems go away without fighting the platform every week? Is the current system blocking growth? Is downtime unacceptable? Budget shapes the path. Fancy can wait. Trust can’t.

There’s no prize for loyalty to a bad theme. There’s also no prize for burning a working site because a redesign felt exciting. We’ll say which way the evidence points.

A simple kickoff kit you can assemble tonight

• One paragraph on what the business does
• Primary audience and primary action
• Three example sites or spots (like / don’t like), with one sentence each
• Logo files and any brand notes
• List of must-have pages or features
• Hard dates and a budget range
• Known logins or known gaps
• Names of decision makers
• Ugly truths you’re willing to say out loud
• Any old commercial, photos, or PDFs that still run the business

If that’s all you bring, we can start. Really. Perfect briefs are rare. Honest folders are common — and enough.

What you can leave at home

Fear that you’re “not technical enough.” A hundred-page RFP copied from the internet. A demand for unlimited revisions with no scope. A promise that you’ll “know it when you see it” with no examples. A competitor teardown that assumes you have their budget. Those slow things down.

Curiosity is welcome. Half-formed ideas are welcome. “We’re not sure” is welcome when it’s honest. “We need it to look expensive but we can’t spend much” is welcome if we can turn it into a phased plan — less welcome if it’s a demand for magic.

Also leave at home the assumption that the previous vendor was either a villain or a genius. Most inherited situations are ordinary: people got busy, passwords got lost, good intentions piled up. We’ll sort it without a courtroom drama.

How the meeting usually runs

We listen more than we pitch. We ask about customers, offers, constraints, and ownership. We look at what you brought. We may screen-share the current site and poke at forms, mobile menus, and obvious trust leaks — not to embarrass you, but to ground the conversation in reality.

You’ll hear options in plain language. You’ll hear what can wait. You’ll hear if hosting or domain cleanup should come before aesthetics. You’ll leave with next steps, not just vibes.

If we need a follow-up for a deeper technical audit, we’ll say so. Kickoff doesn’t have to solve every mystery in one hour. It has to stop the guessing.

After kickoff

You should leave with a clearer path: what’s in phase one, what’s later, what we need next from you, and how communication will work. If you leave only with vibes, the kickoff failed — ask for the path in writing.

Typical next asks from our side: access, content confirmations, example clarifications, a decision on phase boundaries, and a yes/no on hosting or domain cleanup if that’s tangled. Typical next asks from your side: a written summary, a rough timeline, and a sense of cost ranges tied to options — not a mystery number with a smile.

Scope creep loves vagueness. Clarity after kickoff is kindness to future-you.

Failure modes kickoffs are meant to prevent

Building on sand. Pretty homepage, dead form, domain renewing under a personal email. Foundation first when foundation is messy.

Committee surprise. Final design meets the silent partner for the first time. Schedule the silent partner earlier.

Content mirage. Design finishes; words never arrive; launch slips; everyone blames “the website.”

Wishlist inflation. Every idea becomes phase one. Phase one becomes never.

Wrong primary action. Site optimizes for a path the business can’t support. Leads rot. Trust drops.

Asset fiction. Assuming logo files, photos, and brand rules exist when they don’t. Discover in week one, not week five.

If you’re nervous

That’s normal. Especially if the last project went sideways, or if you’re embarrassed by the current site. Disasters are a genre we know. Clean greenfield projects are nice. Untangling the abandoned ones is where a lot of the craft lives.

You don’t have to perform competence. You have to tell the truth about customers, constraints, and cash. We’ll handle the translation into a build path — design, code, launch, hosting if you need it, multimedia if the story needs sound and picture that belong together.

The point

You don’t need a perfect brief. You need a few clear answers, the assets you already have, and the truth about budget and timing. Bring that. We’ll turn it into a path without making you learn our jargon first.

Ready when you are. Bring the messy folder. We’ve opened worse — and we’ve turned plenty of those folders into sites, apps, and quiet hosting setups that finally match how the business actually works. Start with honest answers. The slide deck can stay home.