<p>Custom quotes exist for a reason. The tiers (Essential, Professional, Flagship, E-commerce) are reference points, not ceilings.</p><p>Common custom scenarios:</p><ul><li>Multi-tenant SaaS platform (different from single-business dashboard)</li><li>Complex ERP integration (SAP, NetSuite, Odoo connectivity)</li><li>Real-time analytics or reporting engine</li><li>API-first architecture for third-party integrations</li><li>Hybrid mobile + web system</li></ul><p>We scope these in discovery, then quote based on engineering complexity, timeline, and infrastructure needs. If it's genuinely custom, you get a custom price.</p>

<p>Milestone-based, not time-and-materials:</p><ul><li><strong>Deposit</strong> (typically 30-40% of total): Secures your build window</li><li><strong>Mid-project</strong> (typically 30%): Upon completion of discovery and design approval</li><li><strong>Final</strong> (typically 30%): Upon delivery to production</li></ul><p>No hidden fees. Your quote includes:</p><ul><li>Domain and SSL setup</li><li>Base hosting (Vercel or your infrastructure)</li><li>Deployment and CI/CD</li><li>Post-launch monitoring for 30 days</li></ul><p>Third-party tools (Stripe, Fawry, SMS services, analytics) are only billed if your project actually uses them — and at their standard rates, not marked up.</p>

Yes. This is the entire point of modular architecture. Example: Start with Essential tier (simple website), then 6 months later add Professional features (CMS, integrations, dashboards). The codebase is designed so expansions don't require a rebuild. We track this in a technical roadmap that's part of your handover. Phase 2 work is typically quoted before Phase 1 ends, so you know what the full vision costs and timelines.

We measure against what actually matters to your business: • **Performance**: <1s load time on mobile (Core Web Vitals targets) • **Uptime**: 99.5%+ availability (monitored and reported monthly) • **Conversion**: Forms work, integrations process correctly, customers can complete actions • **Maintainability**: A developer unfamiliar with your codebase can fix bugs in a day We don't guarantee traffic or sales — that's marketing, not engineering. We guarantee the system works, performs, and is maintainable. Post-launch, these metrics are in your monthly maintenance report. If performance degrades, we fix it under the maintenance retainer.

<p>We've built:</p><ul><li><strong>Altruvex.com</strong> — Our own website (Web Engineering, 2025). Built with Next.js, Turborepo, deployed to Vercel.</li><li><strong>NewLight Lighting Store</strong> — E-commerce with Fawry integration, inventory management, multi-tier workflows (2024)</li><li><strong>Art Lighting Store</strong> — E-commerce platform with advanced filtering and performance optimization (2024)</li></ul><p>You can examine these live to understand our engineering standards. We don't use stock imagery or templates — what you see is what we build.</p><p>For more detailed case studies and technical breakdowns, check the Work section on our site.</p>

Because we do the opposite of what most agencies do. You receive your complete source code, full documentation, and zero vendor lock-in by default. If we disappeared tomorrow, your team could maintain it, or hire anyone else to. That's not a feature — it's the only honest way to build. Technically: We use Next.js and Turborepo (both battle-tested at scale), deploy to Vercel or your own infrastructure, and structure every project so a competent developer can understand it in a week. We don't hide behind frameworks or proprietary tooling.

You own everything. All source code, databases, configuration, and credentials are yours from day one. We deliver a handover package that includes: • Complete source code (deployed exactly as it runs in production) • Database schema and migration history • Environment variables and secrets management guide • Deployment documentation (how to redeploy or migrate infrastructure) • Architecture decision log (why we chose each technology) • Runbook for common operations Your code lives in a Git repository you control. We never hold it hostage.

Templates trade flexibility for speed. They're great for specific use cases (Shopify for pure e-commerce, WordPress for blogs). But if your business has custom workflows, local payment integrations, or growth that doesn't fit a plugin architecture, templates hit a ceiling you can't break through. Custom engineering means: • Performance: A Next.js app loads in <1s. WordPress with plugins typically loads in 3-5s. • Integration: We connect directly to your bank's API, Egyptian payment processors, local suppliers — not through a plugin that approximates it. • Ownership: You're not locked into monthly SaaS fees or plugin vendor updates. • Growth: Architecture scales with your business logic, not around a plugin limitation.

Typical timeline: • Week 1: Discovery (requirements, workflows, integrations, scope confirmation) • Week 2-3: Design review and technical architecture approval • Week 4-8: Development, testing, and staging deployment • Week 8-9: Launch, monitoring, and post-launch support Actual timeline depends on complexity. A focused website (Essential tier) might launch in 4 weeks. A full operational system with dashboards and integrations (Flagship tier) typically takes 8-12 weeks. We don't pad timelines. If we think something can be done in 6 weeks, we'll tell you 6 weeks — not 12.

Scope changes are built into our process. We structure projects in phases, so: • Essential features ship first, then integrations, then dashboards. • If you realize you need something different mid-project, we rebuild that phase before moving forward — not after. • We estimate the cost impact upfront so there are no surprises. After launch, the 30-day warranty covers critical fixes. Structural changes move to a maintenance retainer or a new project quote, depending on complexity.

This is core to what we do. We've built integrations with: • Fawry (bill payment and e-commerce) • Vodafone Cash (mobile payments) • Bank transfers (local and SWIFT) • Local delivery and logistics APIs • Arabic-language content and RTL workflows We understand the peculiarities: payment processors that need local IDs, SMS systems that charge per message, hosting that needs local data residency. These aren't afterthoughts — they're part of the architecture from discovery.

True multilingual, not mirrored. Most sites build in English, then translate. We design and engineer for both languages simultaneously: • RTL (right-to-left) is native, not a CSS flip. • Arabic content isn't a translated afterthought — it's an equal-priority experience. • Forms, dashboards, and workflows handle both languages without breaking layouts. • Performance is identical in both languages (no slower Arabic load times). This matters if your customers or employees are primarily Arabic-speaking. A bad Arabic UX loses credibility.

<p>You have three options:</p><ol><li><strong>Maintenance Retainer</strong> (Recommended for most): Essential tier is 2,000 EGP/month, Professional is 4,000 EGP/month. Includes monitoring, security updates, performance optimization, and bug fixes. Typical turnaround for non-critical issues: 2-5 business days.</li><li><strong>As-Needed Support</strong>: No monthly commitment. We bill hourly for changes and fixes (charged at project rates). Typical for businesses that stabilize quickly.</li><li><strong>Bring Your Own Team</strong>: We hand off complete documentation so you or a developer you hire can maintain it independently. We're available for consultations if needed.</li></ol><p>Most clients choose the retainer because it means someone's always watching for performance degradation or security issues.</p>

<p>Yes. That's why we build the way we do.</p><p>The handover package makes it possible for any competent full-stack developer to take over. They'll understand:</p><ul><li>The technology choices (Next.js, databases, deployment strategy)</li><li>The business logic (why workflows are structured the way they are)</li><li>The operational concerns (monitoring, error tracking, scaling)</li></ul><p>We typically do a 4-6 hour knowledge transfer call, then your developer is on their own. Some clients do this immediately after launch; others wait 2 years. It's your call.</p>