Onboarding: how we get started together
Two ways we onboard
Onboarding differs slightly depending on how we work together: Continuous Monthly Development and Fixed Price Projects involve working directly in your systems, while Project Scoping is a planning engagement that usually starts before any system access is needed.
Onboarding for Continuous Monthly Development and Fixed Price Projects
When you sign up for Continuous Monthly Development or a Fixed Price Project online, your Project Manager will contact you the following working day to arrange access and schedule your onboarding meeting.
System access
To develop, test and deploy safely, we typically need:
- Admin access to your system, the website, webshop or application we'll be working on.
- Admin access to your code and deployment setup, FTP, GitHub, or whatever your solution uses.
- Read-only access to your analytics, Google Analytics or the tool you use, so we can see how changes affect your traffic and conversions.
- Access to Google Search Console and Google Tag Manager, where appropriate, so we can make the necessary adjustments for search visibility and tracking.
- Access to your staging server, if you have one.
Your Project Manager will walk you through each item during the onboarding meeting; you don't need to prepare anything in advance.
The onboarding interview
Alongside arranging system access, we conduct an onboarding interview to understand your broader business context. This typically happens alongside your Project Manager introduction and covers four areas:
Your development experience. Have you worked with other developers or agencies before? What worked well, what didn't? Any previous outsourcing experience?
Your expectations and concerns. What challenges might get in the way of project success? Any concerns about our collaboration, location, or time zone differences?
Project goals and success criteria. How will you measure success? Are there critical deadlines we should know about?
Company background. Your company history, your role and decision-making authority, and any other context that helps us understand the project's strategic importance.
This isn't a one-sided conversation: we encourage you to ask questions about our company, services, and processes too. Afterward, we prepare a summary so everyone on your project starts with a shared understanding.
Staging server
As a general rule, every project should have a staging server: a copy of your system where changes are developed and tested before they touch your live environment.
If you don't have one, there are three ways to get one:
- Through your own hosting company. Most hosting companies offer staging environments, and we can advise you on what to request.
- Through 1902 Software. We can provide a staging environment for you. Your Project Manager will give you the price and handle the deployment.
- We set it up together with your hosting company. If you prefer to use your current hosting company, your Project Manager will collaborate with you and them to get it set up and configured.
For very small projects, it's possible to work without a staging server, but it's worth understanding the consequence. Without staging, changes are deployed directly to your live system. If something doesn't work as expected, it affects your live site rather than a test copy, and fixing it becomes more urgent and more visible to your clients. Your Project Manager will explain what this means for your specific project, and the decision is always yours.
Onboarding for Project Scoping
Our project onboarding process for Project Scoping is a little different. We're planning a project rather than working in an existing system, so we usually don't need access to your source code. The exception is when the scoping concerns an upgrade of an existing solution.
Here's what happens:
You're contacted by your Project Manager. Depending on the kind of work, there may be two: for example, one specializing in mobile apps and another in backend systems, if your project spans both. For bigger projects, a software architect often joins at the start of the planning process to make sure everything is designed correctly.
We hold a kickoff meeting. At this meeting, we present the plan for the scoping engagement: what needs to be done, what you're responsible for, what we're responsible for, the timeline, and access to our project management system.
You're introduced to how we work together. We walk you through our project management system and how communication works, and we review practical matters such as the time difference and when it's best to schedule meetings.
Then the scoping work begins. Your Project Manager will tell you approximately how long it will take, though the timeline always depends partly on how quickly decisions and input come from your side.
One practical benefit: everything established during scoping, the communication setup, the meeting rhythm, and the project management access, normally carries straight over into the Fixed Price Project that usually follows.
Switching from another developer
Switching from another developer, freelancer, or agency always takes some effort, but it's something we do regularly.
Software review. Your Project Manager evaluates the existing source code quality and architecture, plugins and dependencies used, existing third-party integrations, and any modifications to the core CMS or platform. This identifies potential issues before we take over, giving you the chance to have your previous developer address critical problems first.
Access and account verification. We request admin login credentials and source code access, access to analytics and monitoring tools, and verification that key accounts (hosting, domain, analytics) are registered under your name rather than tied to your previous supplier. If helpful, we can coordinate directly with your previous supplier to obtain the necessary files and credentials.
For stalled projects, we ask for a list of incomplete tasks to assess fit. For ongoing maintenance takeovers, we typically start with a small batch of tasks, a mix of bug fixes and new features, to confirm we're a good match before committing to ongoing support.
What happens after you sign up for Continuous Monthly Development
If you sign up for Continuous Monthly Development online (Care or Care Plus), here's exactly what happens:
- You complete the sign-up and the first monthly payment of your plan.
- A Project Manager contacts you the following working day.
- Together you arrange system access and schedule your onboarding meeting.
- Your onboarding meeting covers access, priorities and how we work together.
- You start sending tasks, and your software and systems start moving forward.
Let's get you onboarded
The fastest way to start is to book a meeting. We’ll walk you through the service, answer your questions, and get your onboarding scheduled.
Free, no-commitment
Commonly asked questions
How long does onboarding take?
For Continuous Monthly Development, onboarding is typically completed within days. The main variable is how quickly access can be arranged on your side.
For Fixed Price Projects and Project Scoping, onboarding happens as part of the first meetings, so there’s no separate waiting period.
Do we have to have a staging server?
We strongly recommend it, and as a general rule every project should have one. For very small projects it’s possible to work without one, but changes are then deployed directly to your live system. Your Project Manager will explain the consequences for your specific situation, and the decision is yours.
What if we can't provide some of the access you need?
Talk to your Project Manager. Access requirements depend on the work being done, and we’ll find a setup that works, for example, working through your hosting company or your internal IT team.
Is our access information handled securely?
Yes. Access credentials are stored securely, access is limited to the team working on your project, and we’re happy to work within your company’s security requirements, for example, individual user accounts instead of shared credentials.
Book a consultation to explore how AI and 1902 Software can transform your next ecommerce project — faster, smarter, and more cost-efficient.