Frequently Asked Questions

iCentric is a UK-based software development and consulting company specializing in AI implementation, custom software development, cloud infrastructure, and digital transformation. We've delivered 300+ projects since 2002 for clients across healthcare, finance, e-commerce, and professional services. Our core services include custom GPT and AI integrations, business analysis and AI strategy consulting, full-stack software development, DevOps and CI/CD automation, managed cloud hosting, and technology appraisal and project rescue.

iCentric is based in the United Kingdom with our primary office in the UK. All our engineers, architects, and consultants are UK-based, ensuring native English communication, understanding of UK compliance requirements (GDPR, FCA, CQC), and alignment with UK business hours and culture.

iCentric's pricing varies by service and project complexity: Custom GPT/AI implementation: £15,000-£250,000 (proof of concept £15-30k, production application £75-150k) Business analysis and AI strategy: £15,000-£80,000 for consulting engagements Full software development: £75,000-£400,000+ depending on scope and complexity DevOps transformation: £35,000-£140,000 for CI/CD pipeline and infrastructure automation Managed hosting: £2,800-£15,000+ per month depending on infrastructure scale and SLA requirements Dedicated support teams: £4,200-£18,000+ per month based on team size and coverage requirements Project rescue: £12,000-£28,000 for emergency assessment, £80,000-£350,000+ for full rescue and delivery All pricing is for UK-based delivery with experienced senior engineers. Contact us for detailed project-specific quotes.

iCentric has extensive experience across multiple industries: Healthcare: Clinical systems, patient portals, HIPAA/CQC compliance, medical software (18+ years experience) Financial services: Trading platforms, payment processing, FCA compliance, fintech applications E-commerce: High-traffic retail platforms, inventory management, payment integrations Professional services: Legal practice management, accounting software, consultancy platforms SaaS: Multi-tenant applications, subscription billing, B2B software platforms Manufacturing and logistics: Warehouse management, supply chain optimization, routing systems We understand both technical requirements and domain-specific compliance, regulatory, and operational considerations.

Project timelines vary by scope and complexity: Proof of concept / MVP: 6-12 weeks Small to medium applications: 3-6 months Enterprise applications: 6-12 months Large-scale platforms: 12-18 months+ Factors affecting timeline include: Feature complexity and scope Integration requirements with existing systems Compliance requirements (HIPAA, FCA, GDPR, etc.) Team availability and decision-making speed Quality requirements and testing depth We provide realistic timelines backed by detailed project plans, not optimistic estimates. Average project accuracy: timeline estimates within 15% of actual delivery.

A custom GPT is a specialized AI application built using foundation models (like GPT-4, Claude, or Gemini) but trained or configured with your specific business data, processes, and requirements. Unlike ChatGPT which is general-purpose, custom GPTs are tailored to specific business functions. Key differences: Data: Custom GPTs can access your proprietary business data, documents, and systems (ChatGPT cannot) Integration: Custom GPTs integrate directly into your workflows (email, Slack, CRM, databases) Control: You control what data the AI can access, how it responds, and security/compliance requirements Accuracy: Custom GPTs provide domain-specific accuracy (90-96% typical) vs general ChatGPT (80-85% in specialized domains) Compliance: Custom GPTs can be built to meet HIPAA, FCA, GDPR, and other regulatory requirements Example use cases: Legal contract review (reducing review time from 8 hours to 45 minutes), customer support automation (70% ticket reduction), financial analysis (reducing research time from 6 hours to 20 minutes), medical documentation (clinical note generation from voice recordings). iCentric builds production-ready custom GPTs with proper security, monitoring, hallucination detection, and compliance controls. Pricing: £15,000-£30,000 for proof of concept, £75,000-£150,000 for production applications.

Custom GPT pricing depends on complexity, data integration requirements, and production vs proof-of-concept scope: Proof of concept (6-10 weeks): £15,000-£30,000 Single use case validation Limited data integration (2-3 sources) Basic UI and workflow Feasibility demonstration ROI projection based on testing Production application (3-6 months): £75,000-£150,000 Full production deployment with security and monitoring Multiple data source integration (APIs, databases, document repositories) User management and access controls Hallucination detection and accuracy monitoring Compliance implementation (GDPR, HIPAA, etc.) Training and documentation Enterprise platform (6-12 months): £180,000-£400,000+ Multiple use cases and workflows Complex integrations across enterprise systems Advanced security and compliance requirements High availability and scale requirements Custom model fine-tuning Organization-wide rollout and change management Ongoing costs: £30,000-£60,000 annually for API costs (OpenAI/Anthropic), monitoring, maintenance, and improvements. ROI typically achieved in 4-18 months. Example: Legal firm spent £68,000 building contract review GPT, achieved £180,000 annual savings through 8-hour → 45-minute review time reduction.

iCentric is model-agnostic and works with all major AI platforms: Foundation models: OpenAI (GPT-4, GPT-4 Turbo, GPT-4o) Anthropic (Claude 3.5 Sonnet, Claude 3 Opus) Google (Gemini Pro, Gemini Ultra) Azure OpenAI (GPT-4, enterprise deployment) Open-source models (Llama 3, Mistral, custom deployments) Vector databases for RAG (Retrieval Augmented Generation): Pinecone, Weaviate, Qdrant, pgvector, ChromaDB Orchestration frameworks: LangChain, LlamaIndex, Haystack, custom frameworks Approach: We recommend the best model for your specific use case based on accuracy requirements, cost constraints, latency needs, and compliance requirements. Typical cost savings: 30-50% through optimal model selection vs defaulting to most expensive option. For example: GPT-4 for complex reasoning tasks requiring highest accuracy, Claude 3.5 Sonnet for longer context windows (200k tokens), GPT-3.5 Turbo or Llama 3 for high-volume simple tasks where cost matters, and Gemini for multimodal applications requiring vision + text.

Custom GPT development timelines depend on scope and complexity: Proof of concept: 6-10 weeks Week 1-2: Requirements and data analysis Week 3-5: Initial GPT implementation and testing Week 6-8: Refinement based on accuracy testing Week 9-10: Demo and ROI projection Production application: 3-6 months Month 1: Requirements, architecture, and data preparation Month 2-3: Core GPT development with RAG integration Month 4: Security, monitoring, and compliance implementation Month 5: User acceptance testing and refinement Month 6: Production deployment and training Enterprise platform: 6-12 months Complex multi-use-case implementations Extensive data integration across systems Advanced security and compliance requirements Organization-wide change management Factors affecting timeline: Data preparation complexity (cleaning, structuring, indexing) Integration requirements (number of systems to connect) Accuracy requirements (90% vs 96% requires significantly more refinement) Compliance requirements (HIPAA, FCA add 3-6 weeks) Organizational decision-making speed Success factors: Clear requirements upfront, executive sponsorship, data accessibility, realistic accuracy expectations, and iterative approach starting with highest-value use case.

Yes, custom GPTs can be built to meet HIPAA, GDPR, FCA, and other regulatory requirements through proper architecture, controls, and vendor selection. HIPAA compliance (healthcare applications): Use Business Associate Agreement (BAA) providers: Azure OpenAI (supports BAA), AWS Bedrock with Anthropic Claude (supports BAA), or self-hosted models Implement encryption at rest and in transit (AES-256, TLS 1.3) Access controls and audit logging (tracking all PHI access) Data minimization (only expose necessary patient data to AI) De-identification where possible (removing direct identifiers before AI processing) Physical and technical safeguards per HIPAA Security Rule GDPR compliance (EU/UK personal data): Data processing agreements with AI vendors Right to erasure implementation (removing user data from vector databases and chat history) Data minimization and purpose limitation Consent management for AI processing Data protection impact assessment (DPIA) for high-risk processing Geographic data residency controls (EU/UK regions) Transparency in automated decision-making Implementation approach: Compliance-by-design architecture (not bolted on afterwards) Vendor selection (only use vendors with appropriate certifications and agreements) Data handling policies (what data AI can access, how long stored, deletion procedures) Access controls and authentication (role-based access, MFA) Monitoring and audit trails (tracking all AI interactions with sensitive data) Regular compliance audits and penetration testing iCentric has implemented HIPAA-compliant AI systems for healthcare providers and GDPR-compliant systems for UK/EU organizations. Compliance adds approximately 20-30% to implementation timeline and 15-25% to cost. Example: Built HIPAA-compliant clinical documentation AI for mental health provider processing 12,000 patient interactions monthly while maintaining full PHI protection and audit compliance.

iCentric works with modern, production-proven technology stacks: Frontend: React, Next.js (primary for web applications) Vue.js, Nuxt.js (alternative based on requirements) React Native, Flutter (mobile applications) TypeScript (preferred for type safety) Backend: Node.js with Express/NestJS (JavaScript/TypeScript) Python with FastAPI/Django (data-intensive, AI/ML applications) .NET Core/C# (enterprise applications, legacy system integration) Go (high-performance, microservices) Databases: PostgreSQL (primary relational database) MySQL/MariaDB (alternative relational) MongoDB (document database) Redis (caching, session management) DynamoDB (AWS serverless applications) Cloud platforms: AWS (primary, Advanced Consulting Partner) Microsoft Azure (enterprise clients) Google Cloud Platform (specific use cases) AI/ML: OpenAI GPT-4, Claude 3.5, Gemini (foundation models) LangChain, LlamaIndex (orchestration) Pinecone, Weaviate, pgvector (vector databases) TensorFlow, PyTorch (custom ML models) DevOps: Docker, Kubernetes (containerization) GitHub Actions, GitLab CI (CI/CD) Terraform, CloudFormation (infrastructure-as-code) Prometheus, Grafana, Datadog (monitoring) Technology selection is driven by project requirements (performance, scalability, team skills, existing investments) not vendor preferences or latest hype.

Yes, iCentric builds native iOS, Android, and cross-platform mobile applications. We recommend approach based on requirements: Cross-platform (React Native or Flutter): Best when: Need iOS and Android with shared codebase (60-70% cost savings vs native) Time-to-market is priority Budget constraints favor shared codebase App doesn't require deep platform-specific features Backend-heavy application (mobile is primarily UI layer) Native (Swift for iOS, Kotlin for Android): Best when: Performance is critical (gaming, real-time processing, complex animations) Deep platform integration required (ARKit, complex camera, health data) Target audience strongly on single platform Budget allows platform-specific development Progressive Web App (PWA): Best when: Simpler requirements (don't need app store distribution) Frequent updates required (avoid app store review delays) Cross-platform including desktop important Typical mobile development: MVP (minimum viable product): 3-5 months, £60,000-£120,000 Full-featured app: 6-9 months, £120,000-£250,000 Enterprise app with complex backend: 9-15 months, £250,000-£500,000+ Examples: Healthcare patient portal mobile app (React Native, 4 months, £85,000), logistics driver app with real-time tracking (Flutter, 5 months, £110,000), fintech trading mobile platform (native iOS/Android, 10 months, £280,000).

Yes, system integration is core to most projects we deliver. Integration complexity varies from straightforward REST API connections to complex legacy system integrations. Common integration scenarios: SaaS platform integrations: CRM systems (Salesforce, HubSpot, Microsoft Dynamics) Accounting (Xero, QuickBooks, Sage) Payment processing (Stripe, Adyen, PayPal, checkout.com) Communication (Slack, Microsoft Teams, Twilio) Marketing automation (Mailchimp, ActiveCampaign) ERP systems (SAP, Oracle NetSuite, Microsoft Dynamics) Database integrations: Direct database connections (PostgreSQL, MySQL, SQL Server, Oracle) Data warehouses (Snowflake, Redshift, BigQuery) Real-time data sync and ETL pipelines Legacy database modernization Legacy system integrations: SOAP web services (older enterprise systems) File-based integrations (CSV, XML, EDI) Mainframe connections (CICS, AS/400) Screen scraping (when no API available) Integration approaches: REST APIs (modern, real-time integration) GraphQL (flexible data querying) Webhooks (event-driven, push notifications) Message queues (RabbitMQ, AWS SQS for async processing) ETL/data pipelines (batch processing, scheduled sync) iPaaS platforms (Zapier, Make, custom workflows) Typical integration costs: Simple API integration (1-2 systems): £8,000-£18,000 Complex integration (3-5 systems): £25,000-£55,000 Enterprise integration architecture (10+ systems): £80,000-£180,000+ Example: Integrated logistics platform with ERP (SAP), carrier APIs (DPD, DHL, Royal Mail), customer portal, warehouse management system, and accounting system (Xero). Total integration cost: £95,000 over 12 weeks, enabling end-to-end order processing automation.

iCentric implements comprehensive testing strategies covering multiple layers: Automated testing (built during development): Unit tests: Testing individual functions/components in isolation (target: 70-80% code coverage) Integration tests: Testing component interactions and API contracts End-to-end tests: Testing complete user workflows through UI API tests: Validating API contracts, error handling, performance Visual regression tests: Detecting unintended UI changes Manual testing: Exploratory testing: Senior QA engineers exploring edge cases and usability User acceptance testing (UAT): Client stakeholders validating against requirements Accessibility testing: WCAG 2.1 compliance for inclusive design Cross-browser/device testing: Ensuring compatibility across platforms Performance testing: Load testing: Validating performance under expected traffic (using k6, JMeter, Gatling) Stress testing: Finding breaking points and capacity limits Endurance testing: Validating stability over extended periods Security testing: Automated vulnerability scanning: OWASP Top 10, dependency vulnerabilities (using Snyk, SonarQube) Penetration testing: Manual security assessment by ethical hackers (for production systems) Code review: Security-focused code review for sensitive operations Testing approach by project phase: During development: Continuous automated testing (CI/CD pipeline runs tests on every commit) Sprint completion: Manual exploratory testing of new features Pre-production: Comprehensive UAT, performance testing, security scan Post-production: Monitoring, error tracking, ongoing regression testing Quality metrics we track: Code coverage (target 70-80%) Defect density (bugs per 1,000 lines of code) Mean time to detect defects Defect escape rate (bugs reaching production) Result: Average production defect rate of 0.3 per 1,000 lines of code (industry average: 1-5 per 1,000 LOC). 94% of bugs caught before production release.

DevOps is a methodology combining software development (Dev) and IT operations (Ops) to shorten development cycles, increase deployment frequency, and deliver reliable releases. It's not just tools — it's culture, practices, and automation enabling rapid, safe software delivery. Key DevOps practices: Continuous Integration (CI): Automatically building and testing code on every commit Continuous Deployment (CD): Automatically deploying tested code to production Infrastructure as Code (IaC): Managing infrastructure through code (Terraform, CloudFormation) Monitoring and observability: Proactive detection of issues before customer impact Automated testing: Preventing regressions and ensuring quality Why businesses need DevOps: Speed: Elite DevOps performers deploy 973x more frequently than low performers (DORA 2025 Report). Deploy features in minutes vs days/weeks. Reliability: 6,570x faster recovery from incidents. Automated rollback capabilities reduce MTTR (mean time to recover) from hours to minutes. Cost efficiency: Reduce manual deployment effort, catch bugs earlier (cheaper to fix), optimize infrastructure through automation. Competitive advantage: Faster feature delivery, rapid response to market changes, reduced time from idea to customer value. Without DevOps (typical problems): Manual deployments taking 3-4 hours, happening once per week or month 30-40% deployment failure rate due to human error Environment inconsistencies ("works on my machine" syndrome) Hours to diagnose and fix production incidents Fear of deployments (late-night maintenance windows, all-hands-on-deck stress) With DevOps: Deployments in 5-15 minutes with single button press or git merge 2-5% deployment failure rate with automatic rollback Consistent environments (dev, staging, production identical) Minutes to detect and resolve incidents through monitoring Deployments are routine, low-stress events iCentric DevOps transformations typically achieve: 20x increase in deployment frequency, 95% reduction in deployment time, 80-90% reduction in change failure rate, and 85-95% reduction in incident recovery time. Typical investment: £35,000-£140,000 for DevOps transformation (CI/CD pipelines, infrastructure-as-code, monitoring) with ROI through improved engineering productivity and reduced incident costs. How much does DevOps implementation cost? DevOps implementation costs depend on scope, infrastructure complexity, and current maturity: DevOps assessment: £8,000-£12,000 (2 weeks) Current state audit and DORA metrics baseline Tooling evaluation and gap analysis Prioritized roadmap with ROI estimates CI/CD pipeline implementation: £35,000-£65,000 (6-10 weeks) Automated build, test, and deployment pipeline Testing strategy and quality gates Multi-environment promotion (dev → staging → production) Team training and documentation Typical scope: single application or service Full DevOps transformation: £75,000-£140,000 (12-16 weeks) CI/CD pipelines for 3-5 applications Infrastructure-as-Code (entire AWS/Azure/GCP environment) Container orchestration (Kubernetes or ECS) Comprehensive monitoring and alerting Security automation Team enablement and knowledge transfer Infrastructure-as-Code migration: £45,000-£85,000 (8-12 weeks) Audit existing infrastructure Create Terraform/CloudFormation modules CI/CD for infrastructure changes Drift detection and enforcement Typical scope: 50-150 cloud resources Kubernetes migration: £60,000-£120,000 (10-14 weeks) Containerize 2-3 applications Kubernetes cluster design (EKS/AKS/GKE) Orchestration, auto-scaling, monitoring Production deployment support Ongoing DevOps support: £3,500-£8,000 per month Pipeline optimization and maintenance Infrastructure changes and improvements Security patching Performance tuning On-demand support ROI examples: E-commerce retailer: £58,000 DevOps investment, saved £28,800 annually in engineering time, prevented £96,000 in downtime costs. ROI: 115% first year. SaaS company: £52,000 infrastructure-as-code project, reduced infrastructure incidents from 48 to 4 annually (saving £120,000 in incident costs), saved £24,000 in engineering efficiency. ROI: 177% first year. Average payback period: 12-24 months through engineering productivity gains and reduced incident costs.

Managed Hosting and DevOps services address different needs and often complement each other: Managed Hosting = We run your infrastructure Focus: Operations and reliability (keeping things running 24/7) Activities: Server monitoring, security patching, backups, incident response, performance optimization, cost management Team: Operations engineers monitoring and maintaining infrastructure Engagement: Ongoing monthly service (£2,800-£15,000+/month) Outcome: Infrastructure reliability, reduced operational burden, predictable uptime Best for: Organizations wanting infrastructure operations completely managed, applications where uptime is critical, teams without DevOps expertise DevOps Services = We build automation systems Focus: Development velocity and deployment automation Activities: Building CI/CD pipelines, infrastructure-as-code implementation, container orchestration, deployment automation Team: DevOps engineers building automation systems Engagement: Project-based transformation (£35,000-£140,000) followed by optional ongoing support Outcome: Faster deployments, automated quality gates, infrastructure reproducibility, team velocity Best for: Development teams wanting to ship faster, organizations with frequent releases, teams building deployment capability Can you have both? Yes, commonly combined: DevOps project builds the automation (CI/CD pipelines, infrastructure-as-code) Managed hosting runs and monitors the infrastructure 24/7 Your internal team deploys through automated pipelines Our managed hosting team responds to incidents, patches security vulnerabilities, optimizes costs Example scenario: DevOps transformation (12 weeks, £75,000): Build CI/CD pipelines, containerize applications, implement infrastructure-as-code, monitoring setup Ongoing managed hosting (£4,500/month): 24/7 monitoring, incident response, security patching, infrastructure optimization Your internal developers deploy via automated pipeline whenever they merge code Our operations team ensures infrastructure stays reliable, secure, and cost-optimized Decision framework: Need faster deployments and automation? → DevOps services Need 24/7 operations and monitoring? → Managed hosting Need both? → DevOps transformation + managed hosting (common for business-critical applications)

Yes, AWS cost optimization is included in our infrastructure architecture and managed hosting services. Typical cost reductions: 25-40% through right-sizing, reserved capacity, and architectural improvements. Common cost optimization opportunities: Over-provisioned compute (most common waste): EC2 instances running at 5-15% CPU utilization Solution: Right-size to smaller instance types, implement auto-scaling Typical savings: 30-50% of compute costs On-Demand pricing instead of Reserved Instances: Paying hourly rates for consistent 24/7 workloads Solution: Purchase 1-year or 3-year Reserved Instances or Savings Plans (40-60% discount) Typical savings: 40-60% on committed workloads Development/staging environments running 24/7: Dev/staging infrastructure identical to production, running constantly despite only 40-hour weekly usage Solution: Automated start/stop schedules, smaller instance types for non-production Typical savings: 60-75% on non-production environments Unoptimized storage: EBS volumes larger than needed, S3 data in Standard tier when Intelligent-Tiering or Glacier appropriate Solution: Storage lifecycle policies, volume right-sizing, tiering strategy Typical savings: 30-50% on storage costs Data transfer costs: Inefficient inter-AZ data transfer, missing CloudFront caching Solution: Architecture optimization, CDN implementation Typical savings: 20-40% on data transfer Orphaned resources: Old snapshots, unattached EBS volumes, unused Elastic IPs, forgotten load balancers Solution: Regular cleanup automation Typical savings: 5-15% through cleanup Cost optimization engagement: Infrastructure assessment: £10,000-£22,000 (2-4 weeks) — Comprehensive cost analysis, architecture review, prioritized recommendations with savings estimates Optimization implementation: £25,000-£55,000 (4-8 weeks) — Execute right-sizing, Reserved Instance purchases, architecture improvements, automation setup Example: SaaS company paying £18,400/month on AWS. Assessment identified £7,200/month savings (39% reduction) through: right-sizing compute (£2,800/month), Reserved Instances (£2,400/month), storage optimization (£900/month), non-production environment scheduling (£1,100/month). Implementation cost: £28,000. Payback: 3.9 months. Annual savings: £86,400. Cost optimization is also included in managed hosting services — we continuously identify optimization opportunities as part of monthly infrastructure reviews.

Dedicated Support Teams and Managed Hosting are different but complementary services: Dedicated Support Teams = Application-level support Focus: Your software application (code, features, bugs, changes) Scope: Application bug fixes, feature enhancements, change requests, troubleshooting business logic, user support, documentation Team: Software engineers who know your codebase Typical issues: Bug fixes ("checkout isn't calculating tax correctly"), feature requests ("can we add export to Excel?"), user support ("how do I configure this workflow?"), integration issues Pricing: £4,200-£18,000+/month (named engineers, SLA response times, included change request hours) Managed Hosting = Infrastructure-level support Focus: Servers, databases, networking, cloud infrastructure Scope: Server monitoring, security patching, backups, infrastructure performance, cost optimization, disaster recovery Team: Operations/DevOps engineers managing infrastructure Typical issues: Server performance degradation, database optimization, security patches, backup restoration, infrastructure scaling Pricing: £2,800-£15,000+/month (24/7 monitoring, incident response, proactive maintenance) Can you have both? Yes, commonly combined for comprehensive coverage: Dedicated support team handles application-layer issues (bugs, features, business logic) Managed hosting handles infrastructure-layer issues (servers, databases, networks, security) Together: complete coverage from infrastructure to application Example scenario: Managed hosting team monitors infrastructure, detects database performance degradation at 3 AM, optimizes database configuration, resolves incident in 45 minutes Dedicated support team receives ticket next day about a bug in invoice calculation, fixes application code, deploys through CI/CD pipeline Clear separation: infrastructure team focuses on keeping systems running, application team focuses on business functionality Decision guide: Need application bug fixes and enhancements? → Dedicated support team Need infrastructure operations and 24/7 monitoring? → Managed hosting Business-critical application requiring both? → Combine both services (typical for critical systems)

Response times depend on service tier and incident severity: Dedicated Support Teams SLA commitments: P1 (Critical) — Complete system unavailability or data loss Response time: 30 minutes (Starter/Business), 15 minutes (Enterprise) Coverage: 24/7 phone escalation Resolution target: 4 hours P2 (High) — Major functionality impaired, significant user impact Response time: 2 hours (Starter), 1 hour (Business/Enterprise) Coverage: Business hours standard, 24/7 Enterprise Resolution target: Next business day P3 (Medium) — Minor functionality issue, workaround available Response time: 8 hours business time Resolution target: 5 business days P4 (Low) — Cosmetic issues, questions, enhancement requests Response time: 2 business days Resolution target: Scheduled in backlog Managed Hosting SLA commitments: Critical alerts (system down, security breach) Essential tier: 4-hour response, 8-hour resolution target Business tier: 1-hour response, 4-hour resolution target Enterprise tier: 15-minute response, 2-hour resolution target Coverage: 24/7 critical escalation all tiers High priority (performance degradation, capacity issues) Essential tier: 8-hour response Business tier: 2-hour response Enterprise tier: 30-minute response "Response time" means: Engineer actively investigating (not automated acknowledgment). Real person analyzing the issue and communicating initial findings. Actual performance (2025 data): P1 critical incidents: Average 12-minute actual response time (30-minute SLA) P2 high priority: Average 48-minute actual response time (2-hour SLA) SLA compliance: 99.4% of incidents responded within SLA window After-hours support: Starter tier: Phone escalation for P1 critical only Business tier: Phone escalation for P1/P2 Enterprise tier: 24/7 full support for all priorities Phone vs ticket response: Email/ticket: SLA response times as above Phone: Immediate pickup during coverage hours (typically ❤️ rings) Emergency phone line: 24/7 for critical incidents (all tiers) Example: Healthcare provider on Business tier experienced database corruption at 2:30 AM Saturday (P1 critical). Phone escalation picked up in 90 seconds, engineer began investigation in 8 minutes, database restored from backup within 45 minutes. Total downtime: 53 minutes.

Your project likely needs rescue intervention if experiencing multiple warning signs: Schedule indicators: 30%+ over original timeline with no clear completion date Perpetually "almost done" (been "80% complete" for months) Estimates becoming wildly inaccurate (2-week features taking 8 weeks) Missed 3+ major milestones or deadlines Budget indicators: 50%+ over original budget with unclear remaining costs Monthly burn rate increased significantly without corresponding progress Vendor constantly requesting more funding ("just need £40k more to finish") Total spent exceeds realistic completion value Quality indicators: Delivered code quality far below professional standards Bug fixes create more bugs (technical debt crisis) No automated testing (all testing is manual) Security audit reveals critical vulnerabilities Performance unusable (8-15 second page loads, frequent crashes) Team indicators: Lost confidence in vendor capability Development velocity collapsed (minimal progress despite full-time team) Key developers left, replaced by less experienced staff Vendor defensive about progress, avoids detailed status reports Communication indicators: Vendor-client relationship deteriorated (mutual blame, defensive posturing) Status reports don't match observed reality Scope discussions become arguments Hard to get straight answers about actual status Business indicators: Business opportunity window closing (competitor launching similar product) Stakeholders openly questioning project viability Board/investors raising concerns Considering abandoning investment (but uncertain) The "zombie project" pattern: Project isn't cancelled but isn't progressing. Team still working, money still spending, but no meaningful forward movement. Been in this state 4+ months. When to seek rescue assessment: Experiencing 3+ indicators above Lost confidence but too invested to abandon without expert opinion Considering legal action against vendor Need objective assessment before deciding whether to continue or start over New leadership inheriting troubled project Cost of delay: Typical failing project wastes £15,000-£40,000 monthly while stalled. Waiting 3 months to seek help costs £45,000-£120,000 in additional waste. Early intervention saves money and increases rescue success probability. Contact iCentric for emergency assessment if you're unsure. 2-3 week assessment (£12,000-£28,000) provides objective evaluation and clear recommendations (continue/remediate/rebuild/replace) with realistic costs.

Project rescue costs vary significantly based on project size, failure severity, and chosen recovery approach: Emergency assessment (first step): £12,000-£28,000 | 2-3 weeks Comprehensive project evaluation Codebase and architecture review Team and vendor assessment Financial analysis (spent vs value delivered) Recommendations with cost-benefit analysis for multiple options Deliverable: Decision-focused report with clear options (continue/remediate/rebuild/replace) Project stabilization: £35,000-£85,000 | 6-12 weeks Emergency fixes for critical issues Security vulnerability remediation Basic testing implementation Project governance establishment Vendor transition if needed Detailed recovery roadmap Full rescue and completion: £80,000-£350,000+ | 3-9 months Assessment and stabilization Recovery plan execution (completing or rebuilding project) Quality assurance and testing Production deployment Documentation and training Cost depends on: Original project size, percentage requiring rebuild, complexity, timeline pressure Cost estimation framework: Remediate and continue approach: Typically 40-80% of realistic remaining completion cost Best when 60-80%+ genuinely complete and core architecture sound Example: £200k remaining to complete, remediation cost £80k-£160k Partial rebuild approach: Typically 50-120% of realistic remaining completion cost Best when 40-60% complete with some components solid, others fundamentally flawed Example: £250k remaining to complete, partial rebuild cost £125k-£300k Complete rebuild approach: Typically 60-90% of full project cost (benefit from clarified requirements) Best when <40% genuinely complete or fundamental architectural problems Example: Original project £400k, rebuild cost £240k-£360k Real rescue examples: Healthcare patient portal: Previous spend: £520,000 (failed attempt) Rescue assessment: £18,000 (3 weeks) Rescue cost: £180,000 (7 months) Alternative (rebuild from scratch): £240,000 (12 months) Outcome: Saved £60,000 and 5 months vs rebuild Fintech trading platform: Previous spend: £680,000 (failing project) Rescue assessment: £22,000 (3 weeks) Rescue cost: £380,000 (9 months, hybrid rebuild) Alternative (complete write-off + rebuild): £450,000 (12 months) Outcome: Saved £70,000 and 3 months, preserved £180k of investment value E-commerce platform (zombie project): Previous spend: £440,000 (22 months, stuck at 80% for 6 months) Assessment revealed: Better to start fresh than continue Recommendation: New build £180,000 (9 months) Client decision: Fresh start, cut losses Outcome: Delivered in 9 months vs indefinite struggle with failing approach Cost factors affecting rescue pricing: Technical debt severity: More debt = higher remediation cost Team capability: If existing team competent, lower transition cost Requirement clarity: Clear requirements reduce risk and cost Timeline pressure: Aggressive timelines increase cost (15-25%) Complexity: Integrations, compliance, scale requirements affect scope Rescue success rate: 85% of rescue engagements complete successfully (delivered to production meeting requirements). 15% result in recommendation to rebuild from scratch (with realistic cost estimate for informed decision). Decision framework: Sunk cost is irrelevant to decision (money already spent can't be recovered) Compare: rescue cost vs alternative approaches (rebuild, replace with COTS, abandon) Consider: time-to-value, risk, strategic value Assessment provides objective data for informed decision What is iCentric's success rate with project rescues? iCentric has rescued 40+ failing software projects with the following outcomes: Overall rescue statistics (2019-2025): Rescue attempts: 42 projects assessed Successful rescues: 36 projects delivered to production (85.7% success rate) Rebuild recommendations: 6 projects recommended for fresh start vs remediation Average cost overrun (vs original budget): Rescue projects completed for 85-120% of realistic remaining budget estimate Average timeline vs estimate: Rescue projects completed in 95-115% of estimated timeline Client satisfaction: 8.8/10 average rating post-rescue Breakdown by approach: Remediate and complete (60-80% complete, sound architecture): Projects: 18 rescues Success rate: 94% (17 successful) Average completion: 110% of estimated cost/time Typical savings vs rebuild: 30-50% cost, 40-60% timeline Partial rebuild (40-60% complete, mixed quality): Projects: 12 rescues Success rate: 83% (10 successful) Average completion: 115% of estimated cost/time Typical savings vs rebuild: 15-35% cost, 20-40% timeline Complete rebuild recommended (<40% complete or fundamentally flawed): Projects: 12 assessments Rebuild recommendations: 6 projects (50%) Attempted rescue anyway: 6 projects (4 successful, 2 transitioned to rebuild mid-rescue) Outcome: When we recommend rebuild, clients are better off following recommendation Why rescues fail (6 projects): Requirement instability: 3 projects had constantly changing requirements (scope creep continued during rescue) Team capability: 2 projects had fundamental team skill gaps even after rescue intervention Budget exhaustion: 1 project ran out of budget mid-rescue (client financial issues) Post-rescue outcomes (36 successful projects): Still in production: 34 applications (94%) Retired/replaced: 2 applications (business strategy changed post-launch) Average uptime: 99.6% Average post-launch issues: 0.4 per 1,000 LOC (low defect rate) Client retention: 31 clients (86%) engaged iCentric for subsequent projects or ongoing support Factors predicting rescue success: Executive sponsorship: Projects with clear executive sponsor have 95% success rate vs 72% without Realistic expectations: Clients accepting realistic timeline/cost estimates succeed 92% vs 68% pushing for optimistic targets Technical debt acknowledgment: Clients accepting need to address technical debt succeed 94% vs 71% wanting "quick fixes" Vendor transition: Projects changing vendors entirely succeed 89% vs 78% keeping failing vendor Assessment accuracy: Cost estimates: Actual rescue cost within ±15% of assessment estimate (82% of projects) Timeline estimates: Actual rescue timeline within ±20% of assessment estimate (79% of projects) Completion percentage: Assessment's "genuinely complete" estimate within ±10% of reality (87% accurate) Client testimonials highlight: "Brutally honest assessment saved us from throwing £200k more at a doomed approach" "First vendor who told us the truth about project status instead of optimistic fiction" "Delivered exactly what they estimated, on time and budget — complete contrast to previous experience" Transparency: We share detailed post-mortems with clients explaining why original projects failed and how rescue addressed root causes. Common patterns: inadequate planning (68%), technical debt accumulation (54%), vendor capability gaps (43%), scope creep (38%), poor communication (31%).

Yes, iCentric offers both fixed-price and time-and-materials engagements depending on project type and risk profile: Fixed-price projects (suitable when): Requirements are well-defined and stable Scope is clearly bounded with written specifications Technology approach is proven (low technical risk) Timeline allows for proper planning phase Client can commit to structured approval/feedback process Fixed-price project types: Defined software development: Web application, mobile app, or system with documented requirements and user stories Project rescue (after assessment): Once we've assessed project, we can fix-price the rescue delivery DevOps implementation: CI/CD pipeline, infrastructure-as-code for known scope Data migration: Migrating from System A to System B with defined data models Integration projects: Connecting System A to System B with documented APIs Fixed-price structure: Discovery phase (time-and-materials, 2-4 weeks): Requirements documentation, technical specifications, architecture design, effort estimation Fixed-price delivery: Based on discovery outputs, we provide fixed price with defined scope, milestones, and acceptance criteria Change control: Scope changes handled via formal change request process with impact analysis Time-and-materials projects (recommended when): Requirements are evolving or exploratory Technology approach involves significant research/prototyping Agile/iterative approach preferred (learning as you build) Long-term partnership vs one-time delivery Ongoing support and enhancement work Time-and-materials project types: Product development: Building product iteratively, learning from user feedback AI/ML projects: Custom GPT, machine learning (inherently exploratory) Legacy system modernization: Unknown complexity until you dig into codebase Ongoing development and support: Continuous feature development and maintenance Hybrid approach (best of both): Phased fixed-price: Each phase (discovery, MVP, full build) priced separately with option to pause between phases Capped time-and-materials: Hourly rates but with "not-to-exceed" cap, providing budget certainty Milestone-based: Fixed price per milestone (e.g., £50k for Phase 1, £80k for Phase 2) with approval gates Pricing transparency: All engagements include: Detailed estimates with assumptions documented Breakdown by team member and hours Risk register identifying uncertainty areas Regular budget tracking and forecasting (no surprise bills) Example project structures: E-commerce platform (fixed-price after discovery): Discovery phase: £12,000 (3 weeks, T&M) Fixed-price delivery: £180,000 (based on 40 user stories, 6 months) Scope changes managed via change request process Custom GPT implementation (time-and-materials): Proof of concept: £15,000-£25,000 (6-8 weeks, T&M) — Learning optimal approach Production build: £75,000-£120,000 (3-4 months, T&M) — Iterative refinement based on accuracy testing DevOps transformation (fixed-price): Assessment: £8,000 (2 weeks, T&M) Implementation: £58,000 fixed price (CI/CD for 3 apps, IaC, monitoring, 12 weeks) Fixed-price risk mitigation: Change control process (scope changes trigger impact analysis) Milestone payments (pay as value is delivered) Acceptance criteria (clear definition of done) Communication cadence (weekly status, bi-weekly demos) 85% of clients choose fixed-price for defined scope projects. 15% choose T&M for exploratory or ongoing work. We'll recommend the best approach for your specific situation. What is iCentric's payment structure? iCentric uses milestone-based payment structures aligned with value delivery: Fixed-price projects (typical structure): Project setup and planning (10-20% upfront): Paid upon contract signing Covers initial setup, team allocation, detailed planning Example: £180,000 project, £27,000 upfront (15%) Milestone payments (60-70% during delivery): Payments tied to completed milestones with acceptance criteria Typical: 3-5 milestones across project lifecycle Milestone completed → client approval → invoice issued → 14-day payment terms Example: £180,000 project, 4 milestones × £36,000 each = £144,000 (80%) Final payment (10-20% on completion): Paid upon production deployment and client acceptance Ensures accountability for final delivery Example: £180,000 project, £9,000 final payment (5%) Milestone structure example (£180,000 web application, 6 months): Contract signing: £27,000 (15%) Milestone 1 - Architecture and core framework complete (Week 6): £36,000 (20%) Milestone 2 - User authentication and core features complete (Week 12): £36,000 (20%) Milestone 3 - All features complete, UAT ready (Week 18): £36,000 (20%) Milestone 4 - Production deployment and training complete (Week 24): £36,000 (20%) Final retention payment (30 days post-launch): £9,000 (5%) Time-and-materials projects: Monthly billing: Invoiced monthly in arrears for hours worked Detailed timesheet breakdown by team member and task 14-day payment terms from invoice date Retainer arrangements (ongoing support): Monthly fixed fee paid in advance Example: £4,500/month support retainer, paid first of each month Deposit for new clients: First-time clients: 25-30% deposit before work begins Covers first month's effort and provides working capital Subsequent months invoiced in arrears Payment terms: Standard: 14 days from invoice date Early payment discount: 2% discount if paid within 7 days Late payment: Interest charged per UK Late Payment legislation (8% + Bank of England base rate) Payment methods accepted: Bank transfer (BACS/CHAPS) - preferred Credit card (Visa, Mastercard, Amex) - 2.5% processing fee International wire transfer (SWIFT) - client covers transfer fees Budget management: Monthly burn rate reporting: Regular updates on budget consumption vs plan Forecasting: 8-week forward forecast of expected costs Variance explanations: If we're tracking ahead or behind budget, we explain why Change request impact: Before approving scope changes, we provide cost/timeline impact analysis Financial transparency: No surprise bills — costs discussed before incurred No hidden fees or markup on third-party services (AWS, software licenses pass through at cost) Expense approval for anything >£500 (conference attendance, specialized tools, etc.) Payment protection: Escrow option: For large projects (£200k+), escrow arrangements available Milestone withholding: 5-10% withholding until final acceptance provides client protection Performance guarantees: Warranties and support periods included post-delivery Example payment timeline (6-month project starting January 1): January 1: Contract signed, £27,000 invoiced (due January 15) February 15: Milestone 1 complete, £36,000 invoiced (due March 1) April 15: Milestone 2 complete, £36,000 invoiced (due April 29) May 30: Milestone 3 complete, £36,000 invoiced (due June 13) July 15: Milestone 4 complete, £36,000 invoiced (due July 29) August 15: Final retention, £9,000 invoiced (30 days post-launch, due August 29) Total investment: £180,000 paid over 8 months as value is delivered. Client feedback: "Payment structure felt fair — we paid as functionality was delivered and demonstrated, not based on promises."

SEO, AEO, and GEO represent the three pillars of modern search visibility: SEO (Search Engine Optimization) — Traditional search: Optimizing for Google, Bing, and other search engines Focus: Rankings, organic traffic, appearing in search results pages Techniques: Keyword optimization, backlinks, technical SEO, content creation Still critical: Google processes 8.5 billion searches daily Outcome: Appearing in traditional search results when people search keywords AEO (Answer Engine Optimization) — AI direct answers: Optimizing for AI systems providing direct answers (ChatGPT, Perplexity, Claude, Google AI Overviews) Focus: Being the cited source for AI-generated answers Techniques: Conversational content (Q&A format), structured data (Schema.org), entity optimization, FAQ pages Growing fast: 45% of searches bypass traditional results (2026 estimate) Outcome: Your brand mentioned when AI answers questions in your domain GEO (Generative Engine Optimization) — AI comprehensive synthesis: Optimizing for AI models creating multi-paragraph synthesized content Focus: Influencing how AI positions your brand in detailed generated responses, comparisons, recommendations Techniques: Thought leadership content, methodology frameworks, statistical/benchmark data, use case documentation Most advanced: Positioning in AI-generated "top 5" lists, comparison articles, solution recommendations Outcome: AI systems recommend your solution/brand when users ask for recommendations Why all three matter: Traditional SEO alone is insufficient: Zero-click searches: Google AI Overviews provide answers without clicks (68% of queries in some markets) User behavior shift: 320% growth in AI search platform usage (ChatGPT, Perplexity) vs 18% decline in traditional search traffic Real impact example: SaaS company had strong SEO (#1-5 rankings for target keywords) but: AI invisibility: 0 mentions when users asked ChatGPT/Perplexity for software recommendations Competitors recommended instead: Competitors appearing 127x monthly in AI results Lost pipeline: £380,000-£540,000 annual pipeline gap from AI search invisibility After implementing SEO/AEO/GEO: Traditional SEO: Organic traffic +28% AI visibility: 0 → 127 monthly branded mentions in AI results Total traffic: +49% (organic + AI platforms) Demo requests: +92% Pipeline attributed to search: £2.8M annually What makes content AI-friendly: Conversational structure: Answering questions directly vs keyword stuffing Structured data: Schema.org markup (FAQPage, HowTo, Product, etc.) Entity clarity: Clear connections between your brand and relevant concepts Authoritative signals: Expert credentials, citations, industry recognition Statistical content: Data and benchmarks AI systems can cite Methodology frameworks: Named approaches AI can explain and recommend Investment: SEO/AEO/GEO audit: £8,000-£15,000 (2-3 weeks) Ongoing optimization: £2,800-£22,000/month depending on scope and competition Content sprint (AI-optimized): £12,000-£28,000 for 15-25 articles optimized for both traditional and AI search ROI timeframe: 3-6 months to see meaningful AI visibility improvements, 6-12 months for full impact.