Projects and Costs
The project process at XICTRON follows a structured methodology that has proven itself over more than ten years of B2B work. From initial requirements capture through to go-live and beyond, we accompany every project with clear milestones, transparent communication and realistic time estimates. The following questions give you insight into the typical project workflow and help you better assess the time and organizational framework of your undertaking.
- What does a typical B2B shop project at XICTRON look like? A typical project goes through five phases: In the analysis phase (two to three weeks), we capture requirements, analyze existing systems and create a specification document. The concept phase (two to four weeks) covers information architecture, interface design and technical architecture. During implementation (eight to sixteen weeks), we develop the shop iteratively with regular interim presentations. The testing phase (two to three weeks) includes functional tests, load tests and user acceptance tests. After go-live, a four-week hypercare phase follows with increased availability.
- How long does it take to develop a B2B shop? Project duration depends on scope. A B2B shop with standard functionality, one ERP integration and up to 50,000 products is typically operational within four to six months. More complex projects with multiple interfaces, custom order workflows and international scope typically require six to nine months. However, we deliver a functional prototype within just a few weeks, against which the concept can be validated.
- What happens if requirements change during the project? Changes are normal in the B2B environment, as new requirements frequently emerge from day-to-day operations during development. We work with a structured change request process: every change is documented, evaluated for effort and impact and agreed with you before being incorporated into the project plan. For fixed-price projects, change requests are calculated separately. For time-and-materials projects, they feed into ongoing prioritization.
- What internal resources do I need to provide? For a successful B2B project, you need a subject matter expert who knows the business processes and can make decisions. For the analysis phase, representatives from relevant departments should also be available, such as sales, procurement and IT. The time commitment for your internal staff is typically two to four hours per week during the active project phase. We deliberately keep internal effort low so that your day-to-day business is not disrupted.
- How are progress and quality ensured during the project? Transparency is a core principle of our project work. You receive weekly status updates with progress reports and risk assessments. After each two-week iteration, a working version is deployed to the staging environment for your testing. A shared project board gives you real-time visibility into the current state at all times. Before go-live, we document test results and obtain your formal sign-off.
- What support do I receive after go-live? After go-live, a four-week hypercare phase begins with increased availability and accelerated response times. Subsequently, we offer various maintenance packages that include regular security updates, monitoring, backup management and a defined hourly contingent for bug fixes and minor adjustments. Larger enhancements are handled as standalone projects or on a time-and-materials basis.