# Your First Weeks of a Software Project | Gr8r Studio > What happens in the first weeks of a software project: kickoff, access, a first concept, weekly demos and decisions, and what you should prepare. Source: https://gr8rstudio.com/blog/first-two-weeks-with-a-dev-partner [Hiring a Partner](https://gr8rstudio.com/blog) # Your First Two Weeks With a New Product Partner Tanjim Islam Founder & CEO 路 26 Oct 26 路 5 min read Summarise with AI [Summarise with AI: ChatGPT](https://chatgpt.com/?q=Summarise%20the%20key%20points%20of%20this%20article%20from%20Gr8r%20Studio%2C%20then%20tell%20me%20how%20they%20apply%20to%20my%20product%20or%20workflow%3A%20https%3A%2F%2Fgr8rstudio.com%2Fblog%2Ffirst-two-weeks-with-a-dev-partner)[Summarise with AI: Claude](https://claude.ai/new?q=Summarise%20the%20key%20points%20of%20this%20article%20from%20Gr8r%20Studio%2C%20then%20tell%20me%20how%20they%20apply%20to%20my%20product%20or%20workflow%3A%20https%3A%2F%2Fgr8rstudio.com%2Fblog%2Ffirst-two-weeks-with-a-dev-partner)[Summarise with AI: Perplexity](https://www.perplexity.ai/search?q=Summarise%20the%20key%20points%20of%20this%20article%20from%20Gr8r%20Studio%2C%20then%20tell%20me%20how%20they%20apply%20to%20my%20product%20or%20workflow%3A%20https%3A%2F%2Fgr8rstudio.com%2Fblog%2Ffirst-two-weeks-with-a-dev-partner) On this page 1. [ 01Why do the first two weeks matter so much?](#why-do-the-first-two-weeks-matter-so-much) 2. [ 02What happens at kickoff?](#what-happens-at-kickoff) 3. [ 03What access does the team need in week one?](#what-access-does-the-team-need-in-week-one) 4. [ 04What should you see by the end of week two?](#what-should-you-see-by-the-end-of-week-two) 5. [ 05What does a good weekly demo look like?](#what-does-a-good-weekly-demo-look-like) 6. [ 06What should you watch for in the first two weeks?](#what-should-you-watch-for-in-the-first-two-weeks) 7. [ 07What is your job in the first two weeks?](#what-is-your-job-in-the-first-two-weeks) 8. [ 08Frequently asked questions](#frequently-asked-questions) 9. [ 09About the author](#about-the-author) 10. [ 10Related reading](#related-reading) This article supports [How we work](https://gr8rstudio.com/process)[Discuss your challenge](https://cal.com/tanjim-38/30min) ## TL;DR - Expect a kickoff and access set up in your name. - Expect a written plan for the first piece of work and a first concept or prototype you can react to. - Expect a weekly demo where decisions get made. - Your job is to bring access, examples and quick decisions. This post covers what happens after you sign, the last step in our guide to [hiring an AI engineering partner](https://gr8rstudio.com/blog/hire-ai-engineering-partner). ## Why do the first two weeks matter so much? Because they set the pattern for the rest of the project. If decisions are slow in week one, they will be slow in week ten. If you see nothing until week three, you will probably see little in week twelve. The good news is that the first two weeks are also the easiest time to fix the pattern, because nothing big has been built yet. ## What happens at kickoff? The kickoff turns the brief into a shared plan. Expect a call of an hour or two with the people who will do the work, not only the people who sold it. Illustrative diagram based on this article. Not product UI, not real data. By the end you should have: - **One decision maker** on your side, named in writing. - **The goal for the first piece of work**, in a sentence. For example: "a clickable prototype of the approval screen, tested with three support agents." - **A list of open questions**, with an owner for each. - **A meeting rhythm**: a weekly demo, plus a chat channel for daily questions. The Scrum Guide describes the same idea for its own short work cycles: "Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint" ([The Scrum Guide, November 2020](https://scrumguides.org/scrum-guide.html), fetched 25 Oct 2026). You do not need to use Scrum. You do need a written goal. ## What access does the team need in week one? Access is often where first weeks lose days. Prepare it before kickoff if you can. - **Code and hosting**: a repository and cloud account in your name, with the team invited. - **Design files**: a shared workspace you own. - **Data**: sample records the AI or product will use, with personal details removed where you can. - **Existing systems**: test logins for any tool the product connects to. - **People**: two or three users the team can talk to in week one. Keeping accounts in your name from day one means nothing needs moving later. At Gr8r, clients own everything once it's paid for. ## What should you see by the end of week two? Something you can react to. A clickable prototype, a first working screen, or, for an AI feature, the model running on a sample of your real data with the results laid out. Here is an illustration, not a real client project. A healthcare operations team hires a partner to add an AI summary to its referral screen. By day ten, the team shows twenty real referrals, anonymised, with the AI summary next to each and a mark for right, partly right or wrong. That page tells everyone more than a month of meetings would. For longer research phases, the UK Government Digital Service says "around 4 to 8 weeks is typical" for discovery and "You should not start building your service in discovery" ([GOV.UK Service Manual, How the discovery phase works](https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works), fetched 25 Oct 2026). That guidance is for public services. A startup's first piece is usually shorter, but the rule holds: learn first, then build. ## What does a good weekly demo look like? Short, concrete and ending in decisions. The Scrum Guide puts the purpose of its review meeting as "to inspect the outcome of the Sprint and determine future adaptations." In plain terms: look at what was built, then decide what changes. A good demo has three parts: 1. **Show working screens**, not slides. Click through them live. 2. **Name what is still open**, with a date for each answer. 3. **Write down the decisions** and send them the same day. If you leave a demo without written decisions, ask for them before the end of the day. ## What should you watch for in the first two weeks? Good signs are the same people from the sales call, questions about users and data, something to react to by week two, written decisions, and accounts in your name. | Healthy sign | Warning sign | | ------------------------------------------- | ------------------------------------ | | The people on the sales call are on kickoff | New faces you have never met | | Questions about users and data | Questions only about features | | Something to react to by week two | "Next week" twice in a row | | Decisions written down after each demo | Decisions living in someone's memory | | Accounts in your name | Accounts in the partner's name | The longer list of warning signs is in [red flags when hiring a software partner](https://gr8rstudio.com/blog/red-flags-hiring-a-dev-partner). The engagement model you signed shapes week two as well; see [fixed scope or time and materials for your AI build](https://gr8rstudio.com/blog/fixed-scope-vs-time-and-materials). ## What is your job in the first two weeks? Answer fast. A partner waiting a day for each answer loses a week by Friday. Keep your decision maker free for the weekly demo, send the data you promised, and say early if something feels off. If you want a first piece of work scoped this way, see [product discovery](https://gr8rstudio.com/services/product-engineering) or [talk to us](https://cal.com/tanjim-38/30min). ## Frequently asked questions ### What happens in the first week of a software project? A kickoff call, access to the systems and data the team needs, a written goal for the first piece of work, and early sketches or questions. By the end of the week you should know who decides what, and when you will see something. ### What should you prepare before kickoff? Your one page brief, a named decision maker, access to data and existing systems, a list of users the team can talk to, and any designs or prototypes you already have. ### When should you see working software? Within the first two weeks you should see something you can react to, such as a clickable prototype or a first working screen. After that, expect a demo every week. ### What if the first two weeks go badly? Say so at the weekly demo, in writing. Name what is missing and agree what the next week must show. If the second week looks the same, use the exit terms in your contract. ### Who should attend the weekly demo? The person who makes product decisions, someone who knows the users, and the partner's designer and engineer. Keep it short and end with written decisions. ## About the author **Tanjim Islam** is the founder and CEO of Gr8r Studio. He founded the studio in 2023\. Here he writes about how Gr8r approaches hiring, product design and AI engineering. More on the [About page](https://gr8rstudio.com/about/tanjim-islam). To see what a written review looks like, read our UX audit of Veluno, a supplier onboarding product we built and then reviewed the way we review client products. Built by Gr8r for its own portfolio. Not client work. If you want help with this, [book a 30 minute call](https://cal.com/tanjim-38/30min). ## Related reading - [product discovery](https://gr8rstudio.com/services/product-engineering) - [what product discovery is](https://gr8rstudio.com/blog/what-is-product-discovery) - [fixed scope or time and materials](https://gr8rstudio.com/blog/fixed-scope-vs-time-and-materials) - [hiring an AI engineering partner](https://gr8rstudio.com/blog/hire-ai-engineering-partner) - [who owns the code when you hire a team](https://gr8rstudio.com/blog/ai-ownership-checklist) Written by Tanjim Islam Founder & CEO Share [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fgr8rstudio.com%2Fblog%2Ffirst-two-weeks-with-a-dev-partner)[X](https://x.com/intent/post?url=https%3A%2F%2Fgr8rstudio.com%2Fblog%2Ffirst-two-weeks-with-a-dev-partner&text=Your%20First%20Two%20Weeks%20With%20a%20New%20Product%20Partner) This article supports [How we work](https://gr8rstudio.com/process)[Discuss your challenge](https://cal.com/tanjim-38/30min) ## Keep reading - [ Hiring a Partner 26 Oct 26 11 min read How to Hire an AI Engineering Partner: Step by StepHow to hire an AI engineering partner: write the brief, shortlist, click through their live products and AI in production, agree ownership, and score them.By Tanjim Islam](https://gr8rstudio.com/blog/hire-ai-engineering-partner) - [ Hiring a Partner 26 Oct 26 5 min read 15 Questions to Ask Before Hiring a Software Development CompanyQuestions to ask before hiring a software development company, grouped by call, with what a good answer sounds like and when to walk away.By Tanjim Islam](https://gr8rstudio.com/blog/questions-before-hiring-a-dev-partner) - [ Hiring a Partner 26 Oct 26 5 min read 9 Red Flags When Hiring a Software Development CompanyRed flags when hiring a software development company: nine warning signs, what each looks like on a call, and what to ask before you walk away.By Tanjim Islam](https://gr8rstudio.com/blog/red-flags-hiring-a-dev-partner) ## Book a call with our CEO. Pick a time that suits you. A product idea or a workflow that slows your team down: a clear problem is enough, no full specification needed. 5.0 [11 verified reviews Read them on Contra ](https://contra.com/tanjimislam/reviews) - Tanjim is a great designer without any doubt. I love the way he heard my project details and created the better design I was looking for. I highly recommend Tanjim to other Business owners. Thanks Tanjim 馃 Muhammad Talha 路 Founder, SetFrame - Amazing work as always! Md Nomail Hossain Samir 路 Co-founder, Remarked Design - It was really amazing to work with Tanjim, superfast delivery and amazing work Dhruval Golakiya 路 Founder, Ryplix - It was really amazing to work with Tanjim, Superfast delivery and amazing work, highly recommended for any website design and development Dhruval Golakiya 路 Founder, Ryplix - Tanjim and his team did a great job on the hero section I needed in Framer. Super easy to work with and delivered exactly what I had in mind. Highly recommeded! Muhammad Talha 路 Founder, SetFrame - Tanjim is very good at what he does & super easy to work with. He is a genuinely good guy. I highly recommend him! Md Nomail Hossain Samir 路 Co-founder, Remarked Design - Tanjim is a very talented designer who delivers high-quality work with precision. I hired him to handle client projects for my agency & he exceeded expectations every time. If you need an efficient designer, he is the one to go for! Md Nomail Hossain Samir 路 Co-founder, Remarked Design - Every project I鈥檝e entrusted to Tanjim has exceeded expectations. If you're looking for a top-tier designer who consistently delivers exceptional work, Tanjim is the one. Looking forward to working together on more projects 馃 Md Nomail Hossain Samir 路 Co-founder, Remarked Design - Tanjim is an excellent guy. He is super professional in his work and always goes the extra mile. If you're looking for any UI or Framer work, I highly recommend him! Md Nomail Hossain Samir 路 Co-founder, Remarked Design - Tanjim is the founder of Gr8r studio and his Framer expertise is exactly what you need if you are looking for design and development work. Tanjim goes the extra mile on his projects and his attention to detail makes every website stand out I collaborated with Tanjim on a project and he is my main choice for a design partnership. Miguel Queir贸s 路 Collaborator Your call is with Tanjim Islam, our CEO A free 30-minute conversation about your problem, not a sales pitch. Calendar not loading? [Open the booking page](https://cal.com/tanjim-38/30min) Ask Ali