diff --git a/app/services/[slug]/ExpertisePageClient.tsx b/app/services/[slug]/ExpertisePageClient.tsx
index 0928bc3c..44c98f34 100644
--- a/app/services/[slug]/ExpertisePageClient.tsx
+++ b/app/services/[slug]/ExpertisePageClient.tsx
@@ -13,6 +13,7 @@ const TechDecisionTable = dynamic(() => import("./slug-sections/TechDecisionTabl
const FrameworkComparison = dynamic(() => import("./slug-sections/FrameworkComparison"));
const CustomStackTable = dynamic(() => import("./slug-sections/CustomStackTable"));
const DotnetSections = dynamic(() => import("./slug-sections/DotnetSections"));
+const TechIndustries = dynamic(() => import("./slug-sections/TechIndustries"));
const WhyTechnology = dynamic(() => import("./slug-sections/WhyTechnology"));
const IntroStatement = dynamic(() => import("./slug-sections/IntroStatement"));
@@ -270,6 +271,11 @@ export default function ExpertisePageClient({
{expertise.slug === "dotnet" && }
{expertise.slug === "dotnet" && }
+ {/* Non-dotnet tech pages: Industries section */}
+ {["react", "nextjs", "nodejs", "python", "angular", "flutter", "react-native"].includes(expertise.slug) && (
+
+ )}
+
{/* Tech slugs: Decision tables (dynamically imported) */}
{["nodejs", "react", "python", "angular", "flutter", "react-native"].includes(expertise.slug) && (
@@ -280,8 +286,8 @@ export default function ExpertisePageClient({
)}
- {/* For dotnet: Philosophy section comes early, before TechStack */}
- {expertise.slug === "dotnet" && pageData.philosophy && (
+ {/* Philosophy section — renders for any page with philosophy frontmatter */}
+ {pageData.philosophy && (
= {
],
bottomNote: (
<>
- Many projects use both. A public marketing site on Next.js, an
- authenticated dashboard on React + Vite, sharing the same component
+ Many projects use both. A public marketing site on{" "}
+
+ Next.js
+
+ , an authenticated dashboard on React + Vite, sharing the same component
library and design system. We architect for this pattern regularly.
),
@@ -88,8 +94,22 @@ const comparisonDataMap: Record = {
<>
Most projects aren't purely one framework. We've built systems
where Django handles the main app, FastAPI serves the ML inference
- endpoints, and Flask runs lightweight webhook handlers. The framework
- follows the workload.
+ endpoints, and Flask runs lightweight webhook handlers. For the frontend,
+ we pair Python backends with{" "}
+
+ React
+ {" "}
+ or{" "}
+
+ Next.js
+
+ .
),
},
@@ -120,8 +140,15 @@ const comparisonDataMap: Record = {
bottomNote: (
<>
Some projects use both. A Flutter mobile app for the consumer
- experience, a React Native companion for a partner-facing tool sharing
- the same backend. We architect for this when it makes sense.
+ experience, a{" "}
+
+ React Native
+ {" "}
+ companion for a partner-facing tool sharing the same backend. We
+ architect for this when it makes sense.
),
},
@@ -160,10 +187,30 @@ const comparisonDataMap: Record = {
bottomNote: (
<>
The choice often comes down to team expertise and workload type. Node.js
- dominates when JavaScript teams need full-stack speed. Go wins when
- performance and operational simplicity are the priority. Python is the
- default for anything touching data or ML. We regularly run all three in
- the same system, each handling the workload it's best suited for.
+ dominates when JavaScript teams need full-stack speed with{" "}
+
+ React
+ {" "}
+ or{" "}
+
+ Next.js
+
+ . Go wins when performance and operational simplicity are the priority.{" "}
+
+ Python
+ {" "}
+ is the default for anything touching data or ML. We regularly run all
+ three in the same system, each handling the workload it's best
+ suited for.
),
},
@@ -201,11 +248,17 @@ const comparisonDataMap: Record = {
],
bottomNote: (
<>
- Next.js is the safe default for most React projects due to ecosystem
- size and flexibility. Consider Nuxt if your team is Vue-native.
- Consider Remix if your app is mutation-heavy and you value web-standard
- patterns over framework-specific abstractions. We help teams pick based
- on their actual workload, not hype cycles.
+ Next.js is the safe default for most{" "}
+
+ React
+ {" "}
+ projects due to ecosystem size and flexibility. Consider Nuxt if your
+ team is Vue-native. Consider Remix if your app is mutation-heavy and
+ you value web-standard patterns over framework-specific abstractions.
+ We help teams pick based on their actual workload, not hype cycles.
),
},
@@ -244,10 +297,17 @@ const comparisonDataMap: Record = {
bottomNote: (
<>
Angular excels when structure and consistency across large teams matter
- most. React wins on flexibility and hiring pool. Vue hits a sweet spot
- for smaller teams that want conventions without rigidity. The right
- choice depends on team size, project complexity, and how much
- architectural opinion you want from your framework.
+ most.{" "}
+
+ React
+ {" "}
+ wins on flexibility and hiring pool. Vue hits a sweet spot for smaller
+ teams that want conventions without rigidity. The right choice depends
+ on team size, project complexity, and how much architectural opinion
+ you want from your framework.
),
},
@@ -287,10 +347,17 @@ const comparisonDataMap: Record = {
<>
.NET and Java compete directly for enterprise backends — the choice
often comes down to existing infrastructure and team expertise rather
- than technical superiority. Node.js serves a different niche: full-stack
- velocity for JavaScript teams and I/O-heavy workloads. We see many
- organizations running .NET for core business logic with Node.js handling
- the real-time and API gateway layers.
+ than technical superiority.{" "}
+
+ Node.js
+ {" "}
+ serves a different niche: full-stack velocity for JavaScript teams and
+ I/O-heavy workloads. We see many organizations running .NET for core
+ business logic with Node.js handling the real-time and API gateway
+ layers.
),
},
diff --git a/app/services/[slug]/slug-sections/IntroStatement.tsx b/app/services/[slug]/slug-sections/IntroStatement.tsx
index 4153fa31..4a919722 100644
--- a/app/services/[slug]/slug-sections/IntroStatement.tsx
+++ b/app/services/[slug]/slug-sections/IntroStatement.tsx
@@ -1,24 +1,144 @@
"use client";
+import { type ReactNode } from "react";
import { m } from "framer-motion";
-const introStatements: Record = {
- react:
- "Procedure is a React development company that builds production-grade SPAs, real-time dashboards, and component libraries for fintech, payments, and media companies. Since 2016, Procedure's senior React engineers have shipped interfaces handling millions of transactions for clients including Setu, ESPN, and Pine Labs. Every engineer on a React engagement has 3+ years of production React experience.",
- nextjs:
- "Procedure is a Next.js development company that delivers SEO-optimized, server-rendered applications with sub-second page loads for content-heavy platforms and SaaS products. Over 9 years, the team has built Next.js applications serving millions of users for clients in fintech, media, and hospitality, including Setu and Treebo. Engineers embed directly in client teams, shipping production Next.js code from day one.",
- nodejs:
- "Procedure is a Node.js development company that architects high-throughput APIs, event-driven microservices, and real-time backend systems for transaction-heavy industries. Since 2016, Procedure has delivered 100+ backend systems powering fintech platforms, payment infrastructure, and observability tools for clients including Setu, Pine Labs, and Last9. Teams start within 2-5 business days and operate as embedded extensions of the client's engineering organization.",
- python:
- "Procedure is a Python development company specializing in AI/ML pipelines, data engineering, and backend API systems for enterprises that need production-grade machine learning infrastructure. Since 2016, Procedure's Python engineers have built AI-powered platforms, ETL pipelines, and analytics backends across fintech, healthcare, and SaaS verticals for clients including KredX and Last9. The team brings deep expertise in FastAPI, Django, and ML frameworks like PyTorch and scikit-learn.",
- angular:
- "Procedure is an Angular development company that builds enterprise-grade admin portals, internal tools, and complex form-driven applications where type safety and long-term maintainability are non-negotiable. Since 2016, Procedure has delivered Angular platforms for telecom, fintech, and payments companies including MCLabs and Pine Labs, with client partnerships averaging 3+ years.",
- flutter:
- "Procedure is a Flutter development company that delivers cross-platform mobile and web applications from a single codebase, reducing time-to-market by up to 40% compared to native dual-platform development. Since 2016, the team has launched Flutter applications in hospitality, EdTech, and fintech for clients including Treebo and Timely, with production releases in as few as 12 weeks.",
- "react-native":
- "Procedure is a React Native development company that builds high-performance cross-platform mobile applications for fintech, media, and consumer-facing products where native-quality UX is a hard requirement. Since 2016, Procedure has shipped React Native apps processing real-time data, secure transactions, and media streams for clients including ESPN and KredX.",
- dotnet:
- "Procedure is a .NET development company that builds secure, high-availability backend systems, payment processing platforms, and enterprise APIs on the Microsoft stack. Since 2016, Procedure has delivered .NET solutions handling mission-critical transaction volumes for clients in payments, telecom, and fintech, including Pine Labs and MCLabs.",
+const linkClass = "text-accent hover:text-accent-light transition-colors";
+
+const introStatements: Record = {
+ react: (
+ <>
+ Procedure is a React development company that builds production-grade SPAs,
+ real-time dashboards, and component libraries for fintech, payments, and
+ media companies. Since 2016, Procedure's senior React engineers have
+ shipped interfaces handling millions of transactions for clients including
+ Setu, ESPN, and Pine Labs. Every engineer on a React engagement has 3+ years
+ of production React experience. For projects that need server-side rendering
+ and SEO, we pair React with{" "}
+
+ Next.js
+
+ .
+
+ ),
+ nextjs: (
+ <>
+ Procedure is a Next.js development company that delivers SEO-optimized,
+ server-rendered applications with sub-second page loads for content-heavy
+ platforms and SaaS products. Over 9 years, the team has built Next.js
+ applications serving millions of users for clients in fintech, media, and
+ hospitality, including Setu and Treebo. Engineers embed directly in client
+ teams, shipping production Next.js code from day one. Every Next.js project
+ is backed by our{" "}
+
+ React
+ {" "}
+ and{" "}
+
+ Node.js
+ {" "}
+ engineering depth.
+
+ ),
+ nodejs: (
+ <>
+ Procedure is a Node.js development company that architects high-throughput
+ APIs, event-driven microservices, and real-time backend systems for
+ transaction-heavy industries. Since 2016, Procedure has delivered 100+
+ backend systems powering fintech platforms, payment infrastructure, and
+ observability tools for clients including Setu, Pine Labs, and Last9. Teams
+ start within 2-5 business days and operate as embedded extensions of the
+ client's engineering organization. We often pair Node.js backends with{" "}
+
+ React
+ {" "}
+ or{" "}
+
+ Next.js
+ {" "}
+ frontends for full-stack delivery.
+
+ ),
+ python: (
+ <>
+ Procedure is a Python development company specializing in AI/ML pipelines,
+ data engineering, and backend API systems for enterprises that need
+ production-grade machine learning infrastructure. Since 2016, Procedure's
+ Python engineers have built AI-powered platforms, ETL pipelines, and
+ analytics backends across fintech, healthcare, and SaaS verticals for
+ clients including KredX and Last9. The team brings deep expertise in
+ FastAPI, Django, and ML frameworks like PyTorch and scikit-learn. For
+ full-stack delivery, we pair Python backends with{" "}
+
+ React
+ {" "}
+ or{" "}
+
+ Node.js
+ {" "}
+ frontends.
+
+ ),
+ angular: (
+ <>
+ Procedure is an Angular development company that builds enterprise-grade
+ admin portals, internal tools, and complex form-driven applications where
+ type safety and long-term maintainability are non-negotiable. Since 2016,
+ Procedure has delivered Angular platforms for telecom, fintech, and payments
+ companies including MCLabs and Pine Labs, with client partnerships averaging
+ 3+ years. For enterprise backends, we pair Angular with{" "}
+
+ .NET
+ {" "}
+ or{" "}
+
+ Node.js
+
+ .
+
+ ),
+ flutter: (
+ <>
+ Procedure is a Flutter development company that delivers cross-platform
+ mobile and web applications from a single codebase, reducing time-to-market
+ by up to 40% compared to native dual-platform development. Since 2016, the
+ team has launched Flutter applications in hospitality, EdTech, and fintech
+ for clients including Treebo and Timely, with production releases in as few
+ as 12 weeks. For teams with existing JavaScript expertise, we also offer{" "}
+
+ React Native
+ {" "}
+ as an alternative cross-platform approach.
+
+ ),
+ "react-native": (
+ <>
+ Procedure is a React Native development company that builds high-performance
+ cross-platform mobile applications for fintech, media, and consumer-facing
+ products where native-quality UX is a hard requirement. Since 2016,
+ Procedure has shipped React Native apps processing real-time data, secure
+ transactions, and media streams for clients including ESPN and KredX. Teams
+ with existing{" "}
+
+ React
+ {" "}
+ web apps benefit from shared code and components across platforms.
+
+ ),
+ dotnet: (
+ <>
+ Procedure is a .NET development company that builds secure, high-availability
+ backend systems, payment processing platforms, and enterprise APIs on the
+ Microsoft stack. Since 2016, Procedure has delivered .NET solutions handling
+ mission-critical transaction volumes for clients in payments, telecom, and
+ fintech, including Pine Labs and MCLabs. For real-time and API gateway
+ layers, we complement .NET with{" "}
+
+ Node.js
+ {" "}
+ when the workload demands it.
+
+ ),
};
export default function IntroStatement({ slug }: { slug: string }) {
diff --git a/app/services/[slug]/slug-sections/TechIndustries.tsx b/app/services/[slug]/slug-sections/TechIndustries.tsx
new file mode 100644
index 00000000..d22effad
--- /dev/null
+++ b/app/services/[slug]/slug-sections/TechIndustries.tsx
@@ -0,0 +1,355 @@
+"use client";
+
+import { m } from "framer-motion";
+
+interface IndustryCard {
+ title: string;
+ description: string;
+ href?: string;
+}
+
+interface IndustryData {
+ sectionTitle: string;
+ subtitle: string;
+ industries: IndustryCard[];
+}
+
+const techIndustryData: Record = {
+ react: {
+ sectionTitle: "Industries We Build React Applications For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Trading dashboards, payment interfaces, and portfolio management tools built with React. Real-time data rendering, complex form workflows, and SOC 2-compliant architectures for regulated environments.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "SaaS & Technology",
+ description:
+ "Multi-tenant dashboards, subscription portals, and admin panels. React component libraries that scale across product lines with shared design systems and consistent UX.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "Patient portals, clinical dashboards, and telehealth interfaces built with HIPAA-compliant patterns. Accessible UI components meeting WCAG 2.1 AA standards.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Learning management systems, interactive course platforms, and student dashboards. Real-time collaboration features and progress tracking interfaces.",
+ href: "/industries/education",
+ },
+ {
+ title: "Media & Entertainment",
+ description:
+ "Content management interfaces, streaming dashboards, and editorial tools. High-performance rendering for media-rich applications with complex state management.",
+ },
+ {
+ title: "E-commerce & Retail",
+ description:
+ "Product catalogs, checkout flows, and inventory management dashboards. Server-side rendering for SEO-critical pages paired with client-side interactivity for authenticated experiences.",
+ },
+ ],
+ },
+ nextjs: {
+ sectionTitle: "Industries We Build Next.js Applications For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "SaaS & Technology",
+ description:
+ "Marketing sites with sub-second loads, authenticated dashboards, and API-driven platforms. Next.js handles public SEO pages and private app sections in one codebase.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Compliance-ready portals, investor dashboards, and payment interfaces. Server-side rendering for secure data handling with client-side interactivity where needed.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "Patient-facing portals, appointment systems, and clinical tools. HIPAA-compliant server-side data handling with accessible, fast-loading frontends.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Course platforms, learning portals, and institutional websites. Static generation for content pages with dynamic rendering for personalized student experiences.",
+ href: "/industries/education",
+ },
+ {
+ title: "Media & Publishing",
+ description:
+ "Content-heavy sites, editorial platforms, and digital publications. ISR keeps pages fresh without rebuilds. Headless CMS integration for editorial workflows.",
+ },
+ {
+ title: "E-commerce & Retail",
+ description:
+ "Product catalogs, checkout flows, and headless commerce frontends. Static generation for product pages, server-side rendering for personalized recommendations, and edge caching for global performance.",
+ },
+ ],
+ },
+ nodejs: {
+ sectionTitle: "Industries We Build Node.js Systems For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Payment processing APIs, real-time transaction monitoring, and compliance reporting systems. Event-driven architectures handling high-throughput financial data with audit trails.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "SaaS & Technology",
+ description:
+ "Multi-tenant API platforms, webhook processing, and real-time notification systems. Node.js microservices that scale independently as your user base grows.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "HIPAA-compliant APIs, patient data pipelines, and telehealth backend systems. Secure, auditable data handling with real-time communication capabilities.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Learning platform backends, real-time collaboration APIs, and content delivery systems. WebSocket-powered features for live classrooms and interactive assessments.",
+ href: "/industries/education",
+ },
+ {
+ title: "Logistics & Supply Chain",
+ description:
+ "Real-time tracking APIs, inventory management systems, and IoT data ingestion pipelines. Event-driven architectures processing thousands of location updates per second.",
+ },
+ {
+ title: "E-commerce & Retail",
+ description:
+ "Order processing APIs, product catalog services, and recommendation engines. High-concurrency checkout systems that handle traffic spikes without degradation.",
+ },
+ ],
+ },
+ python: {
+ sectionTitle: "Industries We Build Python Systems For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "Clinical data pipelines, diagnostic AI models, and HIPAA-compliant analytics platforms. Python's ML ecosystem powers predictive models for patient outcomes and drug discovery workflows.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Fraud detection models, algorithmic trading systems, and regulatory reporting pipelines. Python handles everything from real-time risk scoring to historical data analysis.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "SaaS & Technology",
+ description:
+ "AI-powered product features, recommendation engines, and data analytics backends. Django and FastAPI platforms serving millions of API requests with ML inference at the edge.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Adaptive learning algorithms, automated grading systems, and student analytics platforms. NLP-powered content analysis and personalized learning path generation.",
+ href: "/industries/education",
+ },
+ {
+ title: "Manufacturing & IoT",
+ description:
+ "Predictive maintenance models, sensor data pipelines, and quality control automation. Python processes telemetry data from industrial equipment to predict failures before they happen.",
+ },
+ {
+ title: "Energy & Utilities",
+ description:
+ "Demand forecasting models, smart grid optimization, and environmental monitoring systems. Python's scientific computing stack handles time-series analysis and geospatial data processing.",
+ },
+ ],
+ },
+ angular: {
+ sectionTitle: "Industries We Build Angular Applications For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Trading platforms, portfolio dashboards, and compliance portals. Angular's strict typing and enterprise patterns meet the reliability requirements of regulated financial environments.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "Clinical management systems, patient record interfaces, and diagnostic tools. Complex form-driven workflows with validation, role-based access, and HIPAA-compliant data handling.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "SaaS & Technology",
+ description:
+ "Enterprise admin panels, multi-tenant dashboards, and workflow automation tools. Angular's modular architecture scales across product teams with shared component libraries.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Learning management platforms, assessment systems, and institutional portals. Complex data-driven interfaces with real-time updates via RxJS-powered reactive patterns.",
+ href: "/industries/education",
+ },
+ {
+ title: "Government & Public Sector",
+ description:
+ "Citizen-facing portals, case management systems, and regulatory platforms. Angular's accessibility support and enterprise security patterns meet government compliance requirements.",
+ },
+ {
+ title: "Telecom & Networking",
+ description:
+ "Network monitoring dashboards, customer self-service portals, and billing management systems. Real-time data visualization for high-throughput telemetry streams.",
+ },
+ ],
+ },
+ flutter: {
+ sectionTitle: "Industries We Build Flutter Apps For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Mobile banking apps, payment wallets, and investment platforms. Flutter's single codebase delivers consistent, secure experiences on iOS and Android with biometric authentication and encryption.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "SaaS & Technology",
+ description:
+ "Companion mobile apps, field service tools, and multi-platform dashboards. Flutter targets mobile, web, and desktop from one codebase for products that need to reach every screen.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "Patient-facing health apps, telehealth interfaces, and clinical workflow tools. Offline-first architecture for environments with unreliable connectivity, with HIPAA-compliant data handling.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Interactive learning apps, student portals, and assessment tools. Flutter's animation capabilities create engaging educational experiences that work offline on student devices.",
+ href: "/industries/education",
+ },
+ {
+ title: "Travel & Hospitality",
+ description:
+ "Booking apps, guest experience platforms, and loyalty programs. Pixel-perfect branded experiences with offline access for travelers and complex booking workflows.",
+ },
+ {
+ title: "E-commerce & Retail",
+ description:
+ "Shopping apps, product catalogs, and in-store tools. Flutter's rendering engine delivers smooth scroll performance and custom animations that drive engagement and conversion.",
+ },
+ ],
+ },
+ "react-native": {
+ sectionTitle: "Industries We Build React Native Apps For",
+ subtitle:
+ "Domain knowledge that accelerates delivery and reduces risk.",
+ industries: [
+ {
+ title: "Financial Services & Fintech",
+ description:
+ "Mobile banking, payment apps, and portfolio trackers. React Native delivers secure, performant financial apps with biometric auth, real-time data, and code sharing with React web dashboards.",
+ href: "/industries/financial-services",
+ },
+ {
+ title: "SaaS & Technology",
+ description:
+ "Mobile companion apps for web-first SaaS products. Share business logic, API clients, and validation code between your React web app and React Native mobile app.",
+ href: "/industries/saas",
+ },
+ {
+ title: "Healthcare & Life Sciences",
+ description:
+ "Patient engagement apps, health tracking tools, and telehealth clients. HIPAA-compliant data handling with offline capabilities for clinical environments.",
+ href: "/industries/healthcare",
+ },
+ {
+ title: "Education & EdTech",
+ description:
+ "Student mobile apps, assessment tools, and classroom collaboration. Over-the-air updates keep educational apps current without waiting for app store reviews.",
+ href: "/industries/education",
+ },
+ {
+ title: "Media & Entertainment",
+ description:
+ "Content streaming apps, social features, and media-rich experiences. React Native's New Architecture handles smooth video playback and real-time content feeds at 60fps.",
+ },
+ {
+ title: "Travel & Hospitality",
+ description:
+ "Booking apps, check-in tools, and guest experience platforms. Push notifications, location services, and offline access for travelers on unreliable networks.",
+ },
+ ],
+ },
+};
+
+export default function TechIndustries({ slug }: { slug: string }) {
+ const data = techIndustryData[slug];
+ if (!data) return null;
+
+ return (
+
+
+
+ );
+}
diff --git a/app/services/[slug]/slug-sections/WhyTechnology.tsx b/app/services/[slug]/slug-sections/WhyTechnology.tsx
index 85d8bce5..625fd235 100644
--- a/app/services/[slug]/slug-sections/WhyTechnology.tsx
+++ b/app/services/[slug]/slug-sections/WhyTechnology.tsx
@@ -1,10 +1,13 @@
"use client";
+import { type ReactNode } from "react";
import { m } from "framer-motion";
+const lnk = "text-accent hover:text-accent-light transition-colors";
+
interface Benefit {
title: string;
- description: string;
+ description: ReactNode;
}
interface WhyTechnologyData {
@@ -35,13 +38,11 @@ const whyTechnologyContent: Record = {
},
{
title: "Ecosystem Depth",
- description:
- "Over 200,000 npm packages extend React. Whatever your product needs, from data visualization to real-time collaboration, there's a battle-tested library available.",
+ description: (<>Over 200,000 npm packages extend React. Whatever your product needs, from data visualization to real-time collaboration, there's a battle-tested library available. For SSR and SEO, Next.js adds a framework layer on top.),
},
{
title: "Lower Switching Costs",
- description:
- "React's dominance means your codebase stays maintainable even when team members rotate. New hires are productive in days, not weeks.",
+ description: (<>React's dominance means your codebase stays maintainable even when team members rotate. New hires are productive in days, not weeks. The same skills extend to React Native for mobile.),
},
],
},
@@ -67,8 +68,7 @@ const whyTechnologyContent: Record = {
},
{
title: "Incremental Adoption",
- description:
- "Migrating an existing React app to Next.js happens page by page, not all at once. You improve performance and SEO without a risky rewrite.",
+ description: (<>Migrating an existing React app to Next.js happens page by page, not all at once. You improve performance and SEO without a risky rewrite.),
},
{
title: "Edge-ready Performance",
@@ -83,8 +83,7 @@ const whyTechnologyContent: Record = {
benefits: [
{
title: "Full-stack JavaScript",
- description:
- "Node.js lets your frontend and backend engineers share a language. This cuts context-switching overhead, simplifies hiring, and means smaller teams can own more of the product.",
+ description: (<>Node.js lets your frontend and backend engineers share a language. Pair it with React or Next.js on the frontend and smaller teams can own more of the product.),
},
{
title: "Real-time Capabilities",
@@ -119,8 +118,7 @@ const whyTechnologyContent: Record = {
},
{
title: "Data Pipeline Maturity",
- description:
- "Python dominates data engineering and analytics. Teams can build everything from ETL pipelines to predictive models in one language, eliminating the integration tax of multi-language stacks.",
+ description: (<>Python dominates data engineering and analytics. Teams build everything from ETL pipelines to predictive models in one language. For the API layer, we often pair Python with Node.js to handle real-time workloads.),
},
{
title: "Readable, Maintainable Code",
@@ -166,8 +164,7 @@ const whyTechnologyContent: Record = {
},
{
title: "Enterprise Adoption",
- description:
- "Major banks, healthcare systems, and government platforms run Angular. If your buyers or compliance teams ask about your tech stack, Angular is a name they already trust.",
+ description: (<>Major banks, healthcare systems, and government platforms run Angular. If your buyers or compliance teams ask about your tech stack, Angular is a name they already trust. For teams that prefer flexibility over convention, React is the alternative we recommend evaluating.),
},
],
},
@@ -178,8 +175,7 @@ const whyTechnologyContent: Record = {
benefits: [
{
title: "True Cross-platform",
- description:
- "Flutter compiles to native ARM code for iOS and Android from a single codebase. You ship to both app stores simultaneously instead of maintaining two separate engineering teams.",
+ description: (<>Flutter compiles to native ARM code for iOS and Android from a single codebase. You ship to both app stores simultaneously instead of maintaining two separate engineering teams. For JavaScript-native teams, React Native is the alternative we evaluate.),
},
{
title: "50% Lower Dev Cost",
@@ -210,8 +206,7 @@ const whyTechnologyContent: Record = {
benefits: [
{
title: "Reuse Your React Team",
- description:
- "If you already have React engineers, they can build your mobile app. React Native shares the same component model, so your team is productive on mobile within weeks.",
+ description: (<>If you already have React engineers, they can build your mobile app. React Native shares the same component model, so your team is productive on mobile within weeks.),
},
{
title: "Shared Web & Mobile Code",
@@ -251,8 +246,7 @@ const whyTechnologyContent: Record = {
},
{
title: "High-performance Runtime",
- description:
- ".NET consistently outperforms Node.js and Python in throughput benchmarks. For transaction-heavy fintech and payments applications, that performance gap translates to infrastructure savings.",
+ description: (<>.NET consistently outperforms Node.js and Python in throughput benchmarks. For transaction-heavy fintech and payments applications, that performance gap translates to infrastructure savings.),
},
{
title: "Long-term Stability",
diff --git a/app/technologies/angular/layout.tsx b/app/technologies/angular/layout.tsx
index 1d30dade..5c9b001c 100644
--- a/app/technologies/angular/layout.tsx
+++ b/app/technologies/angular/layout.tsx
@@ -15,6 +15,14 @@ export const metadata: Metadata = {
"Angular development services for enterprise web apps, SPAs, and complex dashboards. TypeScript-first, signal-based architecture.",
type: "website",
url: "/technologies/angular",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Angular Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
@@ -22,6 +30,14 @@ export const metadata: Metadata = {
"Angular Development Services | 75+ Clients, 9+ Yrs",
description:
"Angular development services for enterprise web apps, SPAs, and complex dashboards. TypeScript-first, signal-based architecture.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Angular Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/app/technologies/flutter/layout.tsx b/app/technologies/flutter/layout.tsx
index 8f4c26dd..e8a7724e 100644
--- a/app/technologies/flutter/layout.tsx
+++ b/app/technologies/flutter/layout.tsx
@@ -4,7 +4,7 @@ export const metadata: Metadata = {
title:
"Flutter App Development Services | 75+ Clients",
description:
- "Custom Flutter apps for iOS, Android, web, and desktop from one Dart codebase. Impeller rendering, pixel-perfect UI, and 30-40% lower development cost than native.",
+ "Flutter app development for iOS, Android, web, and desktop from one codebase. Pixel-perfect UI, 30-40% lower cost than native.",
alternates: {
canonical: "/technologies/flutter",
},
@@ -12,16 +12,32 @@ export const metadata: Metadata = {
title:
"Flutter App Development Services | 75+ Clients",
description:
- "Custom Flutter apps for iOS, Android, web, and desktop from one Dart codebase. Impeller rendering, pixel-perfect UI, and 30-40% lower development cost than native.",
+ "Flutter app development for iOS, Android, web, and desktop from one codebase. Pixel-perfect UI, 30-40% lower cost than native.",
type: "website",
url: "/technologies/flutter",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Flutter App Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
title:
"Flutter App Development Services | 75+ Clients",
description:
- "Custom Flutter apps for iOS, Android, web, and desktop from one Dart codebase. Impeller rendering, pixel-perfect UI, and 30-40% lower development cost than native.",
+ "Flutter app development for iOS, Android, web, and desktop from one codebase. Pixel-perfect UI, 30-40% lower cost than native.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Flutter App Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/app/technologies/nextjs/layout.tsx b/app/technologies/nextjs/layout.tsx
index 24f302be..d0937a32 100644
--- a/app/technologies/nextjs/layout.tsx
+++ b/app/technologies/nextjs/layout.tsx
@@ -15,6 +15,14 @@ export const metadata: Metadata = {
"Expert Next.js development services for enterprise web apps. SSR, SSG, and full-stack solutions. Talk to engineers, not sales. Free architecture consultation.",
type: "website",
url: "/technologies/nextjs",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Next.js Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
@@ -22,6 +30,14 @@ export const metadata: Metadata = {
"Next.js Development Services | 75+ Clients, 9+ Yrs",
description:
"Expert Next.js development services for enterprise web apps. SSR, SSG, and full-stack solutions. Talk to engineers, not sales. Free architecture consultation.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Next.js Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/app/technologies/nodejs/layout.tsx b/app/technologies/nodejs/layout.tsx
index 5b8101d3..9752049e 100644
--- a/app/technologies/nodejs/layout.tsx
+++ b/app/technologies/nodejs/layout.tsx
@@ -15,6 +15,14 @@ export const metadata: Metadata = {
"Node.js development services for scalable APIs, microservices, and backend systems. Senior engineers, honest architecture guidance.",
type: "website",
url: "/technologies/nodejs",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Node.js Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
@@ -22,6 +30,14 @@ export const metadata: Metadata = {
"Node.js Development Services | 50+ Senior Engineers",
description:
"Node.js development services for scalable APIs, microservices, and backend systems. Senior engineers, honest architecture guidance.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Node.js Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/app/technologies/python/layout.tsx b/app/technologies/python/layout.tsx
index 976a6fd3..3f8ec78c 100644
--- a/app/technologies/python/layout.tsx
+++ b/app/technologies/python/layout.tsx
@@ -4,7 +4,7 @@ export const metadata: Metadata = {
title:
"Python Development Services | 75+ Clients, 9+ Yrs",
description:
- "Python development services for backend systems, APIs, and AI/ML engineering. Django, FastAPI, Flask. Experienced engineers, honest architecture guidance. Talk to the team.",
+ "Python development services for backend systems, APIs, and AI/ML. Django, FastAPI, Flask. Senior engineers, honest guidance. Talk to the team.",
alternates: {
canonical: "/technologies/python",
},
@@ -15,13 +15,29 @@ export const metadata: Metadata = {
"Python development services for backend systems, APIs, and AI/ML engineering. Django, FastAPI, Flask. Talk to engineers, not sales.",
type: "website",
url: "/technologies/python",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Python Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
title:
"Python Development Services | 75+ Clients, 9+ Yrs",
description:
- "Python development services for backend systems, APIs, and AI/ML engineering. Django, FastAPI, Flask. Talk to engineers, not sales.",
+ "Python development services for backend systems, APIs, and AI/ML. Django, FastAPI, Flask. Senior engineers, honest guidance. Talk to the team.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - Python Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/app/technologies/react-native/layout.tsx b/app/technologies/react-native/layout.tsx
index 9ee77a35..022336f0 100644
--- a/app/technologies/react-native/layout.tsx
+++ b/app/technologies/react-native/layout.tsx
@@ -15,6 +15,14 @@ export const metadata: Metadata = {
"Ship one codebase to iOS and Android. React Native development services from India-based engineers with US timezone overlap. New Architecture, Expo, TypeScript.",
type: "website",
url: "/technologies/react-native",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - React Native Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
@@ -22,6 +30,14 @@ export const metadata: Metadata = {
"React Native Development Services | 50+ Engineers",
description:
"Ship one codebase to iOS and Android. React Native development services from India-based engineers with US timezone overlap. New Architecture, Expo, TypeScript.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - React Native Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/app/technologies/react/layout.tsx b/app/technologies/react/layout.tsx
index 830c0efc..0e243520 100644
--- a/app/technologies/react/layout.tsx
+++ b/app/technologies/react/layout.tsx
@@ -4,7 +4,7 @@ export const metadata: Metadata = {
title:
"React Development Services | 75+ Clients, 9+ Years",
description:
- "React development services for web applications, SPAs, dashboards, and component libraries. React 19, TypeScript, production-tested. Talk to engineers, not sales.",
+ "React development services for web apps, SPAs, and dashboards. React 19, TypeScript, production-tested. Talk to engineers, not sales.",
alternates: {
canonical: "/technologies/react",
},
@@ -15,13 +15,29 @@ export const metadata: Metadata = {
"React development services for web applications, SPAs, and dashboards. React 19, TypeScript, production-tested. Talk to engineers, not sales.",
type: "website",
url: "/technologies/react",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - React Development Services",
+ },
+ ],
},
twitter: {
card: "summary_large_image",
title:
"React Development Services | 75+ Clients, 9+ Years",
description:
- "React development services for web applications, SPAs, and dashboards. React 19, TypeScript, production-tested. Talk to engineers, not sales.",
+ "React development services for web apps, SPAs, and dashboards. React 19, TypeScript, production-tested. Talk to engineers, not sales.",
+ images: [
+ {
+ url: "/og-image.png",
+ width: 1200,
+ height: 630,
+ alt: "Procedure - React Development Services",
+ },
+ ],
site: "@procedurehq",
creator: "@procedurehq",
},
diff --git a/content/technologies/angular.mdx b/content/technologies/angular.mdx
index 84b4fa16..83f707a1 100644
--- a/content/technologies/angular.mdx
+++ b/content/technologies/angular.mdx
@@ -36,9 +36,9 @@ technologies:
- Playwright
- GitHub Actions
relatedExpertise:
+ - react
- nextjs
- - nodejs
- - frontend-development
+ - dotnet
process:
- number: 1
title: "Architecture & Discovery (1-2 weeks)"
@@ -85,6 +85,20 @@ faqs:
answer: "Yes. Our engineering team is based in India (Mumbai) with working hours that overlap US EST and PST. We have delivered Angular projects for US clients across fintech, healthcare, and enterprise SaaS. Communication happens over Slack, daily standups, and weekly demos."
- question: "What Angular version do you use for new projects?"
answer: "We use Angular 20+ with standalone components, Signals-based reactivity, and zoneless change detection for all new projects. For existing applications, we help teams upgrade incrementally from older Angular versions, following the official migration path one major version at a time."
+philosophy:
+ title: "Our Approach to Angular Development"
+ subtitle: "We use Angular's structure as an accelerator, not a constraint."
+ blocks:
+ - title: "Structure as Productivity"
+ description: "Angular's opinionated architecture is a feature, not a limitation. When 20 developers work on the same codebase, consistent patterns eliminate the debates that slow teams down. We lean into Angular's conventions rather than fighting them."
+ - title: "Enterprise Patterns That Scale"
+ description: "Dependency injection, reactive forms, and module boundaries exist because enterprise applications get complex. We use these patterns deliberately to keep large Angular codebases navigable and testable as they grow over years."
+ - title: "Migration as Engineering"
+ description: "AngularJS to Angular. Zone.js to Signals. Modules to standalone components. We treat migrations as engineering projects with clear scope, incremental delivery, and zero production downtime, not as speculative rewrites."
+ - title: "Type Safety as Investment"
+ description: "Angular's TypeScript-first approach catches entire categories of bugs at compile time. We enforce strict typing across every project because the cost of type discipline is paid once, while the cost of runtime errors compounds forever."
+ - title: "Long-Horizon Architecture"
+ description: "Angular applications often run for 5-10 years. We make architectural decisions with that horizon in mind: predictable upgrade paths, clean abstractions, and documented decisions that help the team maintaining the app in year five understand choices made in year one."
cta:
title: "Ready to Discuss Your Angular Project?"
description: "Talk directly with engineers, not sales. We will assess fit and give honest next steps."
diff --git a/content/technologies/dotnet.mdx b/content/technologies/dotnet.mdx
index a77979f3..18b0a811 100644
--- a/content/technologies/dotnet.mdx
+++ b/content/technologies/dotnet.mdx
@@ -48,7 +48,9 @@ technologies:
- MediatR
- MassTransit
relatedExpertise:
- - backend-development
+ - python
+ - nodejs
+ - angular
whoWeWorkWith:
title: "When to Choose a .NET Development Company"
audiences:
diff --git a/content/technologies/flutter.mdx b/content/technologies/flutter.mdx
index eea4a860..e3af0ba5 100644
--- a/content/technologies/flutter.mdx
+++ b/content/technologies/flutter.mdx
@@ -38,8 +38,9 @@ technologies:
- Fastlane
- Sentry
relatedExpertise:
+ - react-native
- react
- - python
+ - nodejs
process:
- number: 1
title: "Discovery & Architecture (1-2 weeks)"
@@ -86,6 +87,20 @@ faqs:
answer: "Dart is straightforward for developers coming from Java, C#, TypeScript, or Kotlin. The syntax is familiar and the learning curve is manageable. The harder truth: Dart's ecosystem is smaller than JavaScript's. There are roughly 2.8 million Flutter developers globally vs. 17+ million JavaScript developers. If you need to rapidly build a large team, this matters. Working with a consultancy like us solves this - you get a ready Flutter team without competing in a tight talent market."
- question: "Can you add Flutter to our existing native app?"
answer: "Yes. Flutter's add-to-app feature lets you embed Flutter views inside existing Swift/Kotlin apps. Flutter 3.41 improved this with auto-resizing Flutter views that adapt to content size - previously, you needed fixed dimensions from the native parent. This makes incremental adoption practical: add one Flutter screen, validate the approach, then expand."
+philosophy:
+ title: "Our Approach to Flutter Development"
+ subtitle: "We build Flutter apps that justify the single-codebase promise in production, not just in demos."
+ blocks:
+ - title: "Single Codebase Discipline"
+ description: "Flutter's value proposition is one codebase for multiple platforms. We protect that value aggressively by minimizing platform-specific code, using clean abstraction layers for native integrations, and making architectural choices that keep the shared codebase clean."
+ - title: "Native-Quality UX, Not Native-Mimicking UX"
+ description: "Flutter renders every pixel itself. We use that power to create experiences that feel better than native defaults, not just identical to them. Custom animations, thoughtful transitions, and brand-consistent interfaces across every platform."
+ - title: "Platform-Aware Design"
+ description: "One codebase does not mean one design. We build adaptive layouts that respect platform conventions: Material on Android, Cupertino on iOS, responsive layouts on web. The code is shared, the experience feels native."
+ - title: "Dart as Strength"
+ description: "Dart's smaller ecosystem compared to JavaScript is a real trade-off. We address it by building robust internal libraries, contributing to the Dart community, and choosing Dart-native solutions over JavaScript ports that fight the platform."
+ - title: "No Compromise on Performance"
+ description: "Impeller, tree shaking, deferred components. We use every tool Flutter provides to hit 60fps targets on every platform. Performance testing happens on budget Android devices, not just flagship hardware, because that's where real users are."
cta:
title: "Ready to Discuss Your Flutter Project?"
description: "Talk directly with engineers, not sales. We'll assess fit and give honest next steps."
diff --git a/content/technologies/nextjs.mdx b/content/technologies/nextjs.mdx
index 5676ca6d..f70e8a89 100644
--- a/content/technologies/nextjs.mdx
+++ b/content/technologies/nextjs.mdx
@@ -41,9 +41,9 @@ technologies:
- Sentry
- PostHog
relatedExpertise:
+ - react
- nodejs
- - angular
- - frontend-development
+ - python
whoWeWorkWith:
title: "Is Next.js Right for Your Project?"
audiences:
@@ -132,6 +132,20 @@ faqs:
answer: "Yes. We have migrated Create React App and custom Webpack-based React apps to Next.js. The process is incremental. We convert routes one at a time while keeping your application live. Typical CRA-to-Next.js migration takes 4-8 weeks depending on app size."
- question: "Do you work with US-based teams from India?"
answer: "Yes. Our engineering team is based in India (Mumbai) with working hours overlapping US EST/PST. We have delivered projects for US clients at ESPN, Pine Labs, and other organizations listed on our site. Communication happens over Slack, daily standups, and weekly demos."
+philosophy:
+ title: "Our Approach to Next.js Development"
+ subtitle: "We use Next.js as a delivery framework, not a technology identity. The framework serves the product, not the other way around."
+ blocks:
+ - title: "Framework Decisions Over Framework Debates"
+ description: "Next.js gives you Server Components, static generation, and edge rendering. The hard part is knowing when to use which. We make rendering strategy decisions per-route based on your actual traffic patterns and content freshness needs, not framework defaults."
+ - title: "SEO as a First-Class Concern"
+ description: "Next.js is often chosen for SEO. We treat that seriously: structured data, semantic HTML, Core Web Vitals optimization, and crawl budget management are built into every project, not bolted on before launch."
+ - title: "Deployment-Aware Architecture"
+ description: "We architect Next.js apps knowing where they'll run. Vercel, AWS, Docker, or self-hosted, each deployment target has constraints. We design for yours from the start so there are no surprises at launch."
+ - title: "Incremental Adoption, Not Rewrites"
+ description: "Migrating to Next.js happens page by page. Your existing React app stays live while we convert routes, adopt Server Components where they help, and leave client-side rendering where it makes more sense."
+ - title: "Honest Complexity Assessment"
+ description: "Next.js adds server-side complexity. Not every project benefits from that. We'll tell you when a React SPA with Vite is the simpler, cheaper, and better choice for your situation."
cta:
title: "Ready to Discuss Your Next.js Project?"
description: "Talk directly with engineers, not sales. We will assess fit and give honest next steps."
diff --git a/content/technologies/nodejs.mdx b/content/technologies/nodejs.mdx
index e0aa68a0..6c9b007b 100644
--- a/content/technologies/nodejs.mdx
+++ b/content/technologies/nodejs.mdx
@@ -37,8 +37,8 @@ technologies:
- GitHub Actions
relatedExpertise:
- nextjs
- - angular
- - backend-development
+ - python
+ - react
process:
- number: 1
title: "Architecture and Discovery (1-2 weeks)"
@@ -85,6 +85,20 @@ faqs:
answer: "Yes. We have migrated PHP (Laravel), Ruby on Rails, and legacy Express backends to modern Node.js architecture. The approach is always incremental. We identify the highest-value services for migration first, run old and new systems in parallel, and cut over service by service. No big-bang rewrites. Your application stays live throughout the process."
- question: "Do you work with US-based teams from India?"
answer: "Yes. Our engineering team is based in Mumbai with working hours that overlap US EST and PST. We have delivered backend systems for US-based clients and communicate via Slack, daily standups, and weekly demos. Same tools, same cadence, different timezone."
+philosophy:
+ title: "Our Approach to Node.js Development"
+ subtitle: "We build Node.js systems for production reality, not demo-day impressions."
+ blocks:
+ - title: "API Design Over Development Speed"
+ description: "A well-designed API outlasts the framework it runs on. We invest time in contract design, versioning strategy, and error semantics before writing implementation code. Fast shipping starts with thoughtful design."
+ - title: "TypeScript as Standard"
+ description: "Every Node.js project ships with strict TypeScript. Not because it's trendy, but because runtime type errors in production backends cost more to fix than compile-time checks cost to write. No exceptions."
+ - title: "Observability From Day One"
+ description: "Structured logging, distributed tracing, and health checks are part of the initial scaffold, not post-incident additions. We build backends where the first question after a failure is 'what happened' not 'how do we find out.'"
+ - title: "Right-Sized Services"
+ description: "Not everything needs microservices. Not everything belongs in a monolith. We size services based on team boundaries, deployment frequency, and scaling requirements, not architectural fashion."
+ - title: "Exit-Ready Architecture"
+ description: "Every system we build can be maintained by your team or a different vendor. Clean boundaries, documented decisions, and zero proprietary dependencies. You own everything, always."
cta:
title: "Ready to Discuss Your Node.js Project?"
description: "Talk directly with engineers, not sales. We will assess fit and give honest next steps."
diff --git a/content/technologies/python.mdx b/content/technologies/python.mdx
index 5bc2e29d..acd0f569 100644
--- a/content/technologies/python.mdx
+++ b/content/technologies/python.mdx
@@ -38,9 +38,9 @@ technologies:
- AWS
- GitHub Actions
relatedExpertise:
- - ai-engineering
- nodejs
- - backend-development
+ - react
+ - dotnet
process:
- number: 1
title: "Architecture & Discovery (1-2 weeks)"
@@ -87,6 +87,20 @@ faqs:
answer: "Yes. Our engineering team is based in India (Mumbai) with working hours that overlap US EST and PST. We have delivered Python projects for US clients across fintech, healthcare, and enterprise SaaS. Communication happens over Slack, daily standups, and weekly demos."
- question: "What Python version do you use?"
answer: "Python 3.12+ for all new projects. We use strict type hints across every codebase - they are not optional. For existing applications, we help teams upgrade from older Python versions incrementally, addressing breaking changes and deprecated patterns along the way."
+philosophy:
+ title: "Our Approach to Python Development"
+ subtitle: "We build Python systems that survive the gap between prototype and production."
+ blocks:
+ - title: "Data-First Architecture"
+ description: "Python's strength is data. We design systems around data flows, transformation pipelines, and storage patterns first. Application logic wraps around the data model, not the other way around."
+ - title: "Production ML Over Demo ML"
+ description: "Training a model is 10% of the work. We focus on the 90% that matters: serving infrastructure, monitoring drift, versioning models, handling failures gracefully, and retraining pipelines that run without manual intervention."
+ - title: "Readable Over Clever"
+ description: "Python rewards readability. We write code that junior engineers can understand and senior engineers can extend. Clever one-liners become maintenance burdens. Clear, explicit code compounds in value over time."
+ - title: "Automation as Infrastructure"
+ description: "Python scripts that replace manual work should be treated as infrastructure: tested, monitored, and documented. We build automation that teams can rely on, not fragile scripts that break when someone changes a spreadsheet column."
+ - title: "Framework Pragmatism"
+ description: "Django, FastAPI, and Flask each solve different problems. We pick based on your workload and team, not our preferences. Sometimes the answer is all three in the same system, each handling the workload it was designed for."
cta:
title: "Ready to Discuss Your Python Project?"
description: "Talk directly with engineers, not sales. We will assess fit and give honest next steps."
diff --git a/content/technologies/react-native.mdx b/content/technologies/react-native.mdx
index dd528735..b5815b59 100644
--- a/content/technologies/react-native.mdx
+++ b/content/technologies/react-native.mdx
@@ -45,6 +45,20 @@ relatedExpertise:
- react
- flutter
- nodejs
+philosophy:
+ title: "Our Approach to React Native Development"
+ subtitle: "We build React Native apps as extensions of your web engineering investment, not isolated mobile experiments."
+ blocks:
+ - title: "Web + Mobile Thinking"
+ description: "React Native's value multiplies when treated as part of a unified React ecosystem. We architect shared logic layers, API clients, and validation schemas that work across your React web app and React Native mobile app, maximizing code reuse without forcing awkward abstractions."
+ - title: "Native Performance, Not Native Complexity"
+ description: "The New Architecture exists for a reason. We adopt Fabric, TurboModules, and Hermes from day one because performance gaps between React Native and native are engineering choices, not platform limitations. We close those gaps systematically."
+ - title: "Shared Logic, Native UI"
+ description: "Business logic belongs in shared TypeScript modules. UI belongs on the platform. We resist the temptation to force web patterns into mobile and instead build interfaces that feel native to iOS and Android while keeping the logic layer portable."
+ - title: "Upgrade-Ready Architecture"
+ description: "React Native's release cadence is aggressive. We structure projects so major version upgrades are routine maintenance, not multi-sprint projects. Minimal native module dependencies, Expo-first where possible, and clean abstraction boundaries."
+ - title: "Team Leverage Over Team Size"
+ description: "The right React Native architecture lets a team of 3 deliver what would otherwise require separate iOS, Android, and web teams. We optimize for team leverage, building systems where fewer engineers ship more product across more platforms."
process:
- number: 1
title: "Discovery & Architecture (1-2 weeks)"
diff --git a/content/technologies/react.mdx b/content/technologies/react.mdx
index 3a704427..2004e524 100644
--- a/content/technologies/react.mdx
+++ b/content/technologies/react.mdx
@@ -39,7 +39,7 @@ technologies:
- Sentry
relatedExpertise:
- nextjs
- - frontend-development
+ - react-native
- angular
process:
- number: 1
@@ -87,6 +87,20 @@ faqs:
answer: "Yes. Our engineering team is based in India (Mumbai) with working hours that overlap US EST and PST. We've delivered React projects for US clients across fintech, healthcare, and enterprise SaaS. Communication happens over Slack, daily standups, and weekly demos."
- question: "What React version do you use?"
answer: "React 19 (currently 19.2) for all new projects. We use TypeScript in strict mode across every codebase. For existing applications, we help teams upgrade from older React versions - including class component to hooks migration, React Router upgrades, and React Compiler adoption."
+philosophy:
+ title: "Our Approach to React Development"
+ subtitle: "We treat React as a long-term engineering investment, not a short-term UI library choice."
+ blocks:
+ - title: "Component Thinking Over Page Thinking"
+ description: "We design React systems around reusable, composable components with clear data contracts. This means your team ships faster over time because new features assemble from tested pieces rather than being built from scratch every sprint."
+ - title: "Performance as Architecture"
+ description: "Performance is an architectural decision, not a post-launch optimization. We choose rendering strategies, state management patterns, and code-splitting boundaries during design, not after users complain about load times."
+ - title: "Ownership-Ready Codebases"
+ description: "Every React project we deliver is built for your team to own independently. Typed interfaces, Storybook documentation, and clear module boundaries mean your engineers can extend and maintain the system without depending on us."
+ - title: "Incremental Over Big-Bang"
+ description: "Whether migrating from legacy frameworks or adopting React 19 features, we do it route by route. Your application stays live and your team stays productive throughout every transition."
+ - title: "Honest Technology Choices"
+ description: "Not every project needs React. Not every React project needs Next.js. We recommend the simplest tool that solves your actual problem, even if that means less work for us."
cta:
title: "Ready to Discuss Your React Project?"
description: "Talk directly with engineers, not sales. We will assess fit and give honest next steps."