From fa3d3c6fee9532e9d61db1a43ca04bd9dab9c3bb Mon Sep 17 00:00:00 2001 From: vibemarketerpromax Date: Thu, 12 Feb 2026 16:38:15 +0530 Subject: [PATCH 1/3] fix: Remove em dashes from homepage, equalize engagement model cards - Replace all 17 em dashes with periods, commas, or colons as contextually appropriate - Equalize EngagementModels card descriptions to ~155 chars each for visual alignment --- app/page.tsx | 8 ++++---- components/sections/AboutTeaser.tsx | 4 ++-- components/sections/EngagementModels.tsx | 8 ++++---- components/sections/FAQ.tsx | 6 +++--- components/sections/HowWeWork.tsx | 8 ++++---- components/sections/ValueProposition.tsx | 4 ++-- 6 files changed, 19 insertions(+), 19 deletions(-) diff --git a/app/page.tsx b/app/page.tsx index e30df4e..02ca83c 100644 --- a/app/page.tsx +++ b/app/page.tsx @@ -36,7 +36,7 @@ const faqSchema = { name: "What AI systems do you build?", acceptedAnswer: { "@type": "Answer", - text: "We build production AI systems including LLM applications, AI agents, RAG systems, and AI-enhanced products. From conversational AI to document processing to intelligent automation—we handle the complete development lifecycle from architecture to secure production deployment.", + text: "We build production AI systems including LLM applications, AI agents, RAG systems, and AI-enhanced products. From conversational AI to document processing to intelligent automation. We handle the complete development lifecycle from architecture to secure production deployment.", }, }, { @@ -44,7 +44,7 @@ const faqSchema = { name: "How quickly can you start our AI project?", acceptedAnswer: { "@type": "Answer", - text: "Most AI engagements begin within 2-5 days. We match senior engineers based on your AI requirements and tech stack, then integrate them into your development workflow immediately. No months of discovery—we start building fast.", + text: "Most AI engagements begin within 2-5 days. We match senior engineers based on your AI requirements and tech stack, then integrate them into your development workflow immediately. No months of discovery. We start building fast.", }, }, { @@ -68,7 +68,7 @@ const faqSchema = { name: "Do you only work with large enterprises?", acceptedAnswer: { "@type": "Answer", - text: "No. We work with high-growth startups, scale-ups, and enterprises. What matters is the complexity of the AI challenge and your commitment to shipping production systems. If you need serious AI engineering—not consulting theater—we can help.", + text: "No. We work with high-growth startups, scale-ups, and enterprises. What matters is the complexity of the AI challenge and your commitment to shipping production systems. If you need serious AI engineering, not consulting theater, we can help.", }, }, { @@ -84,7 +84,7 @@ const faqSchema = { name: "How do you handle AI security and compliance?", acceptedAnswer: { "@type": "Answer", - text: "Security is built into every AI system we develop—not bolted on later. We implement secure LLM architectures, prevent prompt injection, ensure data privacy, and meet compliance requirements (SOC 2, HIPAA, GDPR). Our AI security expertise comes from building production systems that enterprises trust.", + text: "Security is built into every AI system we develop. Not bolted on later. We implement secure LLM architectures, prevent prompt injection, ensure data privacy, and meet compliance requirements (SOC 2, HIPAA, GDPR). Our AI security expertise comes from building production systems that enterprises trust.", }, }, ], diff --git a/components/sections/AboutTeaser.tsx b/components/sections/AboutTeaser.tsx index fd2cc82..8b14dbf 100644 --- a/components/sections/AboutTeaser.tsx +++ b/components/sections/AboutTeaser.tsx @@ -15,8 +15,8 @@ export function AboutTeaser() { transition={{ duration: 0.6 }} >

- Seasoned builders delivering software products— - with and without AI. + Seasoned builders delivering software products.{" "} + With and without AI.

Production-tested engineering. Your partner for what's next. diff --git a/components/sections/EngagementModels.tsx b/components/sections/EngagementModels.tsx index d6e2e88..94f9046 100644 --- a/components/sections/EngagementModels.tsx +++ b/components/sections/EngagementModels.tsx @@ -6,7 +6,7 @@ const engagementModels = [ { title: "Team Augmentation", description: - "Senior engineers integrated directly into your engineering organization, reporting to your leadership and delivering against your roadmap.", + "Senior engineers integrated directly into your engineering organization. They report to your leadership and deliver against your roadmap from day one.", features: [ "Full-time dedicated senior engineers", "Seamless adoption of your tech stack and workflows", @@ -32,7 +32,7 @@ const engagementModels = [ { title: "Managed Delivery", description: - "Full ownership of a defined scope—from architecture through deployment. You set the objectives; we deliver production-ready software on schedule.", + "Full ownership of a defined scope, from architecture through deployment. You set the objectives; we deliver production-ready software on schedule.", features: [ "End-to-end technical ownership and accountability", "Dedicated delivery lead with direct stakeholder access", @@ -58,7 +58,7 @@ const engagementModels = [ { title: "AI Transformation", description: - "A strategic partnership to accelerate enterprise AI adoption—from opportunity assessment through production deployment and organizational enablement.", + "A strategic partnership to accelerate enterprise AI adoption. We take you from opportunity assessment through production deployment and enablement.", features: [ "AI readiness and opportunity assessment", "Strategic roadmap with clear ROI milestones", @@ -116,7 +116,7 @@ export function EngagementModels() {

Three proven engagement frameworks designed for different business - objectives. Scale up, scale down, or pivot—without renegotiating + objectives. Scale up, scale down, or pivot. Without renegotiating contracts.

diff --git a/components/sections/FAQ.tsx b/components/sections/FAQ.tsx index cdb546d..6bc73c8 100644 --- a/components/sections/FAQ.tsx +++ b/components/sections/FAQ.tsx @@ -7,12 +7,12 @@ const faqs = [ { question: "What AI systems do you build?", answer: - "We build production AI systems including LLM applications, AI agents, RAG systems, and AI-enhanced products. From conversational AI to document processing to intelligent automation—we handle the complete development lifecycle from architecture to secure production deployment.", + "We build production AI systems including LLM applications, AI agents, RAG systems, and AI-enhanced products. From conversational AI to document processing to intelligent automation. We handle the complete development lifecycle from architecture to secure production deployment.", }, { question: "How quickly can you start our AI project?", answer: - "Most AI engagements begin within 2-5 days. We match senior engineers based on your AI requirements and tech stack, then integrate them into your development workflow immediately. No months of discovery—we start building fast.", + "Most AI engagements begin within 2-5 days. We match senior engineers based on your AI requirements and tech stack, then integrate them into your development workflow immediately. No months of discovery. We start building fast.", }, { question: "How much does AI development cost?", @@ -32,7 +32,7 @@ const faqs = [ { question: "What makes you different from AI consultancies?", answer: - "Traditional AI consultants deliver slide decks and POCs that never ship. We deliver production AI. Our engineers embed with your team, write code daily, and ship AI systems that work. No handoffs, no knowledge silos—just AI that reaches production.", + "Traditional AI consultants deliver slide decks and POCs that never ship. We deliver production AI. Our engineers embed with your team, write code daily, and ship AI systems that work. No handoffs, no knowledge silos. Just AI that reaches production.", }, { question: "Do you work with enterprise clients?", diff --git a/components/sections/HowWeWork.tsx b/components/sections/HowWeWork.tsx index b318ab8..2b3301b 100644 --- a/components/sections/HowWeWork.tsx +++ b/components/sections/HowWeWork.tsx @@ -8,7 +8,7 @@ const processSteps = [ step: "01", title: "Discovery & Alignment", description: - "A focused conversation with our technical leadership to understand your objectives, architecture constraints, and success criteria. You receive an honest assessment—not a sales pitch.", + "A focused conversation with our technical leadership to understand your objectives, architecture constraints, and success criteria. You receive an honest assessment, not a sales pitch.", duration: "30 min", }, { @@ -29,14 +29,14 @@ const processSteps = [ step: "04", title: "Seamless Integration", description: - "Your dedicated engineers integrate directly with your team—participating in standups, adopting your tools, and aligning with your workflows. They operate as true extensions of your engineering organization.", + "Your dedicated engineers integrate directly with your team: participating in standups, adopting your tools, and aligning with your workflows. They operate as true extensions of your engineering organization.", duration: "Ongoing", }, { step: "05", title: "Deliver & Evolve", description: - "Your team ships production-ready code with comprehensive documentation and knowledge transfer. As your requirements evolve, we scale capacity up or down—no long-term lock-ins.", + "Your team ships production-ready code with comprehensive documentation and knowledge transfer. As your requirements evolve, we scale capacity up or down. No long-term lock-ins.", duration: "Continuous", }, ]; @@ -75,7 +75,7 @@ export function HowWeWork() {

A proven engagement process built for enterprise velocity. Your team - gains senior engineering capacity within days—not weeks. + gains senior engineering capacity within days, not weeks.

diff --git a/components/sections/ValueProposition.tsx b/components/sections/ValueProposition.tsx index 437d68e..23834e0 100644 --- a/components/sections/ValueProposition.tsx +++ b/components/sections/ValueProposition.tsx @@ -23,7 +23,7 @@ const values = [ hoverBorder: "hover:border-accent/50", title: "AI That Ships to Production", description: - "From LLM applications to AI agents, you get production-ready AI systems built on deep engineering excellence. No science projects—real products that scale.", + "From LLM applications to AI agents, you get production-ready AI systems built on deep engineering excellence. No science projects. Real products that scale.", }, { icon: ( @@ -67,7 +67,7 @@ const values = [ hoverBorder: "hover:border-accent/50", title: "Your AI Team, Extended", description: - "Senior AI engineers embedded directly with your team—same tools, same standups, same commitment to shipping. You get AI capacity without the hiring overhead.", + "Senior AI engineers embedded directly with your team: same tools, same standups, same commitment to shipping. You get AI capacity without the hiring overhead.", }, ]; From dc580797b4620b71471b614acf84d086831a17f4 Mon Sep 17 00:00:00 2001 From: vibemarketerpromax Date: Thu, 12 Feb 2026 16:56:44 +0530 Subject: [PATCH 2/3] fix: Remove em dashes from services, industries, and remaining site pages --- app/about-us/page.tsx | 12 +- app/ai-safety/page.tsx | 2 +- app/ai-upskill/page.tsx | 14 +-- app/approach/page.tsx | 8 +- app/contact-us/layout.tsx | 4 +- app/contact-us/page.tsx | 6 +- app/culture/page.tsx | 4 +- app/events/page.tsx | 18 +-- app/services/[slug]/ExpertisePageClient.tsx | 20 ++-- app/why-us/page.tsx | 6 +- app/work/CaseStudiesClient.tsx | 2 +- components/footer.tsx | 2 +- content/industries/education.mdx | 16 +-- content/industries/financial-services.mdx | 10 +- content/industries/healthcare.mdx | 8 +- content/industries/saas.mdx | 8 +- content/services/ai-agents.mdx | 12 +- content/services/ai-engineering.mdx | 6 +- content/services/ai-privacy.mdx | 6 +- content/services/ai-security.mdx | 10 +- content/services/backend-development.mdx | 4 +- content/services/cloud.mdx | 10 +- content/services/design-systems.mdx | 12 +- content/services/forward-deployed.mdx | 4 +- content/services/frontend-development.mdx | 18 +-- content/services/kubernetes.mdx | 6 +- content/services/mobile-development.mdx | 2 +- content/services/product-design.mdx | 8 +- content/services/software-testing-and-qa.mdx | 8 +- content/technologies/dotnet.mdx | 28 ++--- content/use-cases/ai-search.mdx | 6 +- content/use-cases/conversational-ai.mdx | 8 +- content/use-cases/document-ai.mdx | 2 +- lib/case-studies-data.ts | 4 +- lib/expertise-data.tsx | 118 +++++++++---------- lib/industries-data.tsx | 42 +++---- 36 files changed, 227 insertions(+), 227 deletions(-) diff --git a/app/about-us/page.tsx b/app/about-us/page.tsx index 29d41c6..2adb84e 100644 --- a/app/about-us/page.tsx +++ b/app/about-us/page.tsx @@ -63,7 +63,7 @@ const values = [ ), title: "Embedded Partnership", description: - "We don't believe in the agency model where contractors disappear after handoff. Our engineers become true extensions of your team—attending your standups, understanding your codebase, and caring about your outcomes. Our certified best workplace culture means you get engaged, fulfilled engineers who stay for the long term.", + "We don't believe in the agency model where contractors disappear after handoff. Our engineers become true extensions of your team, attending your standups, understanding your codebase, and caring about your outcomes. Our certified best workplace culture means you get engaged, fulfilled engineers who stay for the long term.", }, { icon: ( @@ -108,7 +108,7 @@ const values = [ ), title: "Honest Conversations", description: - "No black boxes. No vague timelines. No surprise invoices. We keep it real because feedback isn't about being right—it's about making things better together. Respect and candor travel in both directions.", + "No black boxes. No vague timelines. No surprise invoices. We keep it real because feedback isn't about being right. It's about making things better together. Respect and candor travel in both directions.", }, ]; @@ -205,7 +205,7 @@ export default function AboutPage() { className="text-lg sm:text-xl text-text-secondary leading-relaxed mb-10 max-w-2xl mx-auto" > We are forward-deployed engineers, designers, and thinkers who - stay close to the problem—not tucked behind layers of process. + stay close to the problem, not tucked behind layers of process. From idea to deploy, we move with intent, learn in the open, and keep the "why" visible. @@ -266,7 +266,7 @@ export default function AboutPage() { work better, and that hasn't changed. Today, we're applying our engineering rigor to AI-powered systems, enterprise applications, and complex technical challenges. We still - experiment, break, fix, and ship together—because that's how + experiment, break, fix, and ship together, because that's how real products and real teams grow.

@@ -319,7 +319,7 @@ export default function AboutPage() {

Our founders have more than a decade of experience in their - respective fields. They lead by mentoring, not managing—helping + respective fields. They lead by mentoring, not managing, helping engineers and clients alike grow through real collaboration.

@@ -579,7 +579,7 @@ export default function AboutPage() { Whether you're launching your first AI initiative, scaling an existing product, or trying to rescue a stalled project, we'd love to hear about your challenges. Our team will give you an - honest assessment—even if the answer is that you don't need + honest assessment, even if the answer is that you don't need us yet.

diff --git a/app/ai-safety/page.tsx b/app/ai-safety/page.tsx index 6f747f3..5db0011 100644 --- a/app/ai-safety/page.tsx +++ b/app/ai-safety/page.tsx @@ -103,7 +103,7 @@ const principles = [ number: "05", title: "Security & Robustness", description: - "AI systems face unique attack vectors. We harden against adversarial inputs, prompt injection, data poisoning, and model extraction threats. Red-teaming is not a checkbox—we find vulnerabilities before adversaries do.", + "AI systems face unique attack vectors. We harden against adversarial inputs, prompt injection, data poisoning, and model extraction threats. Red-teaming is not a checkbox. We find vulnerabilities before adversaries do.", icon: ( {/* Important Notice */} @@ -343,7 +343,7 @@ export default function AIUpskillPage() {

We looked at where software engineering is heading in three, five, and ten years. The answer was unanimous: AI. Not as a - buzzword or a feature—but as the foundation of how software + buzzword or a feature, but as the foundation of how software gets built, deployed, and evolved.

@@ -359,7 +359,7 @@ export default function AIUpskillPage() { live and breathe AI - —as both producers and consumers of AI tools. + , as both producers and consumers of AI tools.

@@ -420,7 +420,7 @@ export default function AIUpskillPage() { className="text-lg text-text-secondary max-w-3xl mx-auto" > A comprehensive curriculum covering the full spectrum of AI - engineering—from foundational concepts to production deployment. + engineering, from foundational concepts to production deployment. Every concept is examined through four levers: skills, cost, latency, and performance. @@ -743,7 +743,7 @@ export default function AIUpskillPage() {

Learn from engineers actively building AI systems for enterprise clients. Our instructors bring hands-on experience from real - deployments—not just theoretical knowledge. They've shipped + deployments, not just theoretical knowledge. They've shipped RAG pipelines, agent architectures, and production ML systems.

diff --git a/app/approach/page.tsx b/app/approach/page.tsx index 97f2e2c..cacfd0c 100644 --- a/app/approach/page.tsx +++ b/app/approach/page.tsx @@ -78,7 +78,7 @@ const processPhases = [ tagline: "Ship Incrementally. Learn Continuously.", duration: "Ongoing Sprints", description: - "We work in tight iterations, shipping working software every week. Not features that almost work—features that are deployed, monitored, and ready for users. Our engineers pair program, conduct code reviews, and maintain production-grade standards from the first commit.", + "We work in tight iterations, shipping working software every week. Not features that almost work. Features that are deployed, monitored, and ready for users. Our engineers pair program, conduct code reviews, and maintain production-grade standards from the first commit.", deliverables: [ "Weekly deployable increments", "Continuous integration and deployment", @@ -108,7 +108,7 @@ const processPhases = [ tagline: "Production is Day One, Not the Finish Line", duration: "Milestone-Based", description: - "Getting to production is just the beginning. We instrument everything, monitor performance, and iterate based on real user data. When issues arise—and they will—we're there to diagnose, fix, and improve. Your product gets better every week it's live.", + "Getting to production is just the beginning. We instrument everything, monitor performance, and iterate based on real user data. When issues arise (and they will), we're there to diagnose, fix, and improve. Your product gets better every week it's live.", deliverables: [ "Production deployment and monitoring", "Performance optimization", @@ -285,7 +285,7 @@ const principles = [ number: "06", title: "Users First", description: - "Our compass is simple: make it useful, make it clear. We design for the person on the other side of the screen—not metrics, not trends. Real users, real solutions.", + "Our compass is simple: make it useful, make it clear. We design for the person on the other side of the screen, not metrics, not trends. Real users, real solutions.", }, ]; @@ -975,7 +975,7 @@ export default function ApproachPage() { Outcomes, Not Outputs.

- We measure success by what ships and the impact it creates—not by + We measure success by what ships and the impact it creates, not by hours logged or tickets closed.

diff --git a/app/contact-us/layout.tsx b/app/contact-us/layout.tsx index eb62e82..c772e2a 100644 --- a/app/contact-us/layout.tsx +++ b/app/contact-us/layout.tsx @@ -46,7 +46,7 @@ const contactFAQSchema = { name: "What happens on the strategy call?", acceptedAnswer: { "@type": "Answer", - text: "The strategy call is a focused 30-minute conversation with a senior AI engineer—not a sales rep. We'll discuss your technical requirements, existing infrastructure, and goals. You'll leave with a clear understanding of potential approaches, realistic timelines, and whether Procedure is the right fit for your project.", + text: "The strategy call is a focused 30-minute conversation with a senior AI engineer, not a sales rep. We'll discuss your technical requirements, existing infrastructure, and goals. You'll leave with a clear understanding of potential approaches, realistic timelines, and whether Procedure is the right fit for your project.", }, }, { @@ -70,7 +70,7 @@ const contactFAQSchema = { name: "What if we're not sure what we need?", acceptedAnswer: { "@type": "Answer", - text: "That's exactly what the strategy call is for. Bring your business problem, and our senior engineers will help you identify the right AI approach—whether that's LLM integration, custom models, or AI agents. We'll outline realistic options and timelines based on what you're trying to achieve.", + text: "That's exactly what the strategy call is for. Bring your business problem, and our senior engineers will help you identify the right AI approach, whether that's LLM integration, custom models, or AI agents. We'll outline realistic options and timelines based on what you're trying to achieve.", }, }, ], diff --git a/app/contact-us/page.tsx b/app/contact-us/page.tsx index cd2cdf7..90a4c08 100644 --- a/app/contact-us/page.tsx +++ b/app/contact-us/page.tsx @@ -128,7 +128,7 @@ export default function ContactPage() { {/* Subheadline */}

Whether you need forward-deployed engineers, a rapid AI sprint, - or a full product build—tell us what you're working on and + or a full product build, tell us what you're working on and we'll match you with senior AI talent within 2-5 days.

@@ -416,7 +416,7 @@ export default function ContactPage() { name="message" required rows={5} - hint="Tell us about your AI initiative—what you're building, the problem you're solving, and where you need help." + hint="Tell us about your AI initiative: what you're building, the problem you're solving, and where you need help." /> {/* Submit Button */} @@ -658,7 +658,7 @@ export default function ContactPage() { {[ { q: "What happens on the strategy call?", - a: "The strategy call is a focused 30-minute conversation with a senior AI engineer—not a sales rep. We'll discuss your technical requirements, existing infrastructure, and goals. You'll leave with a clear understanding of potential approaches, realistic timelines, and whether Procedure is the right fit for your project.", + a: "The strategy call is a focused 30-minute conversation with a senior AI engineer, not a sales rep. We'll discuss your technical requirements, existing infrastructure, and goals. You'll leave with a clear understanding of potential approaches, realistic timelines, and whether Procedure is the right fit for your project.", }, { q: "How do you determine pricing?", diff --git a/app/culture/page.tsx b/app/culture/page.tsx index 661fd94..fc9ea6b 100644 --- a/app/culture/page.tsx +++ b/app/culture/page.tsx @@ -360,7 +360,7 @@ export default function CulturePage() { stay close to the problem, not tucked behind layers of process. From idea to deploy, we move with intent, learn in the open, and keep the 'why' visible. Our certified best workplace culture - ensures engineers thrive—not just deliver. + ensures engineers thrive, not just deliver. {/* Stats row */} @@ -512,7 +512,7 @@ export default function CulturePage() {

These aren't corporate values on a poster. These are the beliefs that guide our daily decisions and how we treat each - other—and why we earned our Best Workplace certification. + other. That is why we earned our Best Workplace certification.

diff --git a/app/events/page.tsx b/app/events/page.tsx index edb942a..1733dba 100644 --- a/app/events/page.tsx +++ b/app/events/page.tsx @@ -111,7 +111,7 @@ const involvementOptions = [ ), title: "Support the Community", description: - "Help us keep events free and accessible. Whether it's food, swag, or venue support—your sponsorship directly fuels the community we're building together.", + "Help us keep events free and accessible. Whether it's food, swag, or venue support, your sponsorship directly fuels the community we're building together.", cta: "Become a sponsor", ctaIcon: ( At Procedure, we believe the best ideas emerge when curious people come together. That's why we host free events, workshops, and - meetups—creating spaces where engineers, designers, and founders + meetups, creating spaces where engineers, designers, and founders can learn from each other, share what they're building, and form genuine connections. @@ -320,7 +320,7 @@ export default function EventsPage() { Mumbai Meets AI - Edition 4

- Mumbai Meets AI is our flagship community initiative—a free, + Mumbai Meets AI is our flagship community initiative: a free, monthly meetup that brings together AI practitioners, engineers, and builders. No sales pitches, no corporate speak. Just real conversations about what's working, what's not, and @@ -538,7 +538,7 @@ export default function EventsPage() {

Every event teaches us something new about building community. Here's a look back at the gatherings that brought us - together—and the conversations that continue to shape what we do + together, and the conversations that continue to shape what we do next.

@@ -844,7 +844,7 @@ export default function EventsPage() { { title: "Everyone Has Something to Teach", description: - "Whether you've shipped ten products or you're just getting started, your perspective matters. Our events create space for all voices—not just the loudest ones in the room.", + "Whether you've shipped ten products or you're just getting started, your perspective matters. Our events create space for all voices, not just the loudest ones in the room.", }, { title: "Learning is Better Together", @@ -854,7 +854,7 @@ export default function EventsPage() { { title: "Free Means Accessible", description: - "We keep our events free because knowledge shouldn't have a price tag. No paywalls, no gatekeeping—just show up with curiosity.", + "We keep our events free because knowledge shouldn't have a price tag. No paywalls, no gatekeeping. Just show up with curiosity.", }, { title: "Community Over Competition", @@ -1006,7 +1006,7 @@ export default function EventsPage() {

Our community grows stronger with every new voice. Whether you want to share your expertise, support what we're building, or - simply show up and be part of the conversation—you're welcome + simply show up and be part of the conversation. You're welcome here.

@@ -1069,7 +1069,7 @@ export default function EventsPage() {

We're just getting started. New cities, new formats, new ways to bring builders together. Whether you join us at the next meetup - or connect with us online—we'd love to meet you. + or connect with us online. We'd love to meet you.

diff --git a/app/services/[slug]/ExpertisePageClient.tsx b/app/services/[slug]/ExpertisePageClient.tsx index 8a43d91..6fdf408 100644 --- a/app/services/[slug]/ExpertisePageClient.tsx +++ b/app/services/[slug]/ExpertisePageClient.tsx @@ -40,7 +40,7 @@ interface Props { // Customized booking section copy per expertise const bookingSubtext: Record = { "ai-engineering": - "Share your AI project requirements—from model architecture to MLOps infrastructure. We'll outline a practical path from prototype to production-ready deployment.", + "Share your AI project requirements, from model architecture to MLOps infrastructure. We'll outline a practical path from prototype to production-ready deployment.", "ai-agents": "Tell us about the workflows you want to automate with AI agents. We'll discuss tool integrations, safety guardrails, and a realistic timeline to deployment.", "ai-security": @@ -48,19 +48,19 @@ const bookingSubtext: Record = { "ai-privacy": "Share your compliance requirements and data handling challenges. We'll discuss privacy-preserving architectures and how to meet GDPR, HIPAA, or SOC 2 standards.", "mobile-development": - "Walk us through your mobile app vision—native or cross-platform. We'll help you choose the right approach and plan for a smooth App Store launch.", + "Walk us through your mobile app vision, native or cross-platform. We'll help you choose the right approach and plan for a smooth App Store launch.", "frontend-development": - "Tell us about your web application challenges—whether a new build or performance optimization. We'll discuss framework choices, design implementation, and Core Web Vitals.", + "Tell us about your web application challenges, whether a new build or performance optimization. We'll discuss framework choices, design implementation, and Core Web Vitals.", "backend-development": - "Describe your backend architecture needs—APIs, data pipelines, or scaling challenges. We'll assess the right stack and infrastructure for your growth trajectory.", + "Describe your backend architecture needs: APIs, data pipelines, or scaling challenges. We'll assess the right stack and infrastructure for your growth trajectory.", "software-testing-and-qa": - "Share your testing challenges—flaky tests, missing coverage, or CI/CD gaps. We'll outline a test automation strategy that fits your development workflow.", + "Share your testing challenges: flaky tests, missing coverage, or CI/CD gaps. We'll outline a test automation strategy that fits your development workflow.", "product-design": "Tell us about your AI product and the user experience challenges you face. We'll discuss research methods, prototyping, and design patterns that build user trust.", "kubernetes": - "Describe your container orchestration needs—new clusters, migrations, or operational pain points. We'll assess your workloads and recommend a production-ready approach.", + "Describe your container orchestration needs: new clusters, migrations, or operational pain points. We'll assess your workloads and recommend a production-ready approach.", "dotnet": - "Talk directly with engineers\u2014not sales. We\u2019ll assess fit and give honest next steps.", + "Talk directly with engineers, not sales. We\u2019ll assess fit and give honest next steps.", }; export default function ExpertisePageClient({ @@ -266,7 +266,7 @@ export default function ExpertisePageClient({ @@ -359,7 +359,7 @@ export default function ExpertisePageClient({ {pageData.qualityMatters && ( .NET Project

- Whether modernizing legacy systems or building new—we’re happy to talk through your situation. + Whether modernizing legacy systems or building new, we’re happy to talk through your situation.

diff --git a/app/work/CaseStudiesClient.tsx b/app/work/CaseStudiesClient.tsx index ad844b1..fc30c4b 100644 --- a/app/work/CaseStudiesClient.tsx +++ b/app/work/CaseStudiesClient.tsx @@ -221,7 +221,7 @@ export function CaseStudiesClient({

Every case study started with a conversation. Tell us about your AI challenges, and our engineers will give you an honest - assessment of how we can help—even if that means pointing you in a + assessment of how we can help, even if that means pointing you in a different direction.

diff --git a/components/footer.tsx b/components/footer.tsx index 15dbfa7..a17f488 100644 --- a/components/footer.tsx +++ b/components/footer.tsx @@ -98,7 +98,7 @@ export function Footer() {

AI engineering and security for production systems. Proven - delivery excellence—now focused on AI. + delivery excellence, now focused on AI.

{/* Contact Info */} diff --git a/content/industries/education.mdx b/content/industries/education.mdx index e36eb1a..97f571a 100644 --- a/content/industries/education.mdx +++ b/content/industries/education.mdx @@ -2,7 +2,7 @@ title: "Education" tagline: "Personalized. Accessible. Effective." description: | - Every learner is different—but most educational software treats them the same. We build AI that adapts to individual learners, generates engaging content, and measures what actually matters: learning outcomes. Education technology that works for students, not just administrators. + Every learner is different, but most educational software treats them the same. We build AI that adapts to individual learners, generates engaging content, and measures what actually matters: learning outcomes. Education technology that works for students, not just administrators. heroStats: - value: "45%" label: "Improvement in learning outcomes" @@ -12,7 +12,7 @@ heroStats: label: "Accessibility compliant" challenges: - title: "One Size Doesn't Fit All" - description: "Traditional courseware delivers the same content to every student. But learners have different backgrounds, paces, and styles—AI should adapt to them." + description: "Traditional courseware delivers the same content to every student. But learners have different backgrounds, paces, and styles. AI should adapt to them." icon: "users" - title: "Content Creation is Expensive" description: "Quality educational content takes time and expertise to create. Scaling to new topics, languages, or formats is slow and costly." @@ -32,10 +32,10 @@ solutions: description: "Generate quizzes, explanations, and practice problems at scale. Content creation that keeps up with your curriculum needs." icon: "document" - title: "Intelligent Tutoring Systems" - description: "Build AI tutors that provide personalized guidance—Socratic questioning, worked examples, and feedback tailored to each learner." + description: "Build AI tutors that provide personalized guidance: Socratic questioning, worked examples, and feedback tailored to each learner." icon: "lightbulb" - title: "Automated Assessment & Feedback" - description: "Grade essays, evaluate code, and assess complex work with AI—providing rapid, consistent feedback that helps students improve." + description: "Grade essays, evaluate code, and assess complex work with AI, providing rapid, consistent feedback that helps students improve." icon: "clipboard" - title: "Learning Analytics" description: "Understand how students learn, where they struggle, and what interventions work. Data-driven insights for educators and administrators." @@ -52,11 +52,11 @@ relatedIndustries: - saas faqs: - question: "How does adaptive learning AI actually work?" - answer: "We model learner knowledge state based on their interactions—questions answered, time spent, patterns of errors. The AI uses this model to select optimal next content: easier material to reinforce foundations, or harder challenges when ready to advance." + answer: "We model learner knowledge state based on their interactions: questions answered, time spent, patterns of errors. The AI uses this model to select optimal next content: easier material to reinforce foundations, or harder challenges when ready to advance." - question: "Can AI really grade essays and complex work?" - answer: "For many assessment types, yes—with appropriate human oversight. AI can provide consistent initial evaluation and detailed feedback. We design rubrics and validation processes that maintain assessment quality." + answer: "For many assessment types, yes, with appropriate human oversight. AI can provide consistent initial evaluation and detailed feedback. We design rubrics and validation processes that maintain assessment quality." - question: "How do you ensure accessibility?" - answer: "Accessibility is a design requirement from day one—not a retrofit. We follow WCAG guidelines, test with assistive technology, and involve users with disabilities in our design process." + answer: "Accessibility is a design requirement from day one, not a retrofit. We follow WCAG guidelines, test with assistive technology, and involve users with disabilities in our design process." - question: "What about student data privacy (FERPA/COPPA)?" answer: "We understand education's privacy requirements. We build systems that maintain appropriate data boundaries, obtain necessary consents, and give institutions control over student data." cta: @@ -74,7 +74,7 @@ seo: - **Learning science informed**: We build on research about how people actually learn - **Accessibility commitment**: Inclusive design from the start, not an afterthought - **Scale experience**: We've built platforms serving millions of learners -- **Outcome focus**: We measure what matters—learning gains, not just usage +- **Outcome focus**: We measure what matters: learning gains, not just usage ## Results We've Delivered diff --git a/content/industries/financial-services.mdx b/content/industries/financial-services.mdx index 4da2b83..c9b6139 100644 --- a/content/industries/financial-services.mdx +++ b/content/industries/financial-services.mdx @@ -2,7 +2,7 @@ title: "Financial Services" tagline: "Sub-100ms. SOC 2 compliant. Production-ready." description: | - Financial markets don't wait. Your AI systems shouldn't either. We build AI applications engineered for the demands of finance—real-time processing, bulletproof reliability, and the compliance posture your regulators expect. From trading signals to fraud detection, we ship production AI in days. + Financial markets don't wait. Your AI systems shouldn't either. We build AI applications engineered for the demands of finance: real-time processing, bulletproof reliability, and the compliance posture your regulators expect. From trading signals to fraud detection, we ship production AI in days. heroStats: - value: "$47M+" label: "Fraud prevented for clients" @@ -25,11 +25,11 @@ challenges: icon: "lock" solutions: - title: "Real-Time ML Infrastructure" - description: "We build inference pipelines optimized for latency—model serving, feature stores, and data pipelines that deliver predictions in milliseconds, not seconds." + description: "We build inference pipelines optimized for latency: model serving, feature stores, and data pipelines that deliver predictions in milliseconds, not seconds." icon: "bolt" featured: true - title: "Regulatory-Ready Architecture" - description: "Audit logs, model versioning, decision explainability—compliance requirements built into the architecture, not bolted on after." + description: "Audit logs, model versioning, decision explainability: compliance requirements built into the architecture, not bolted on after." icon: "document" - title: "High-Precision Fraud Detection" description: "Machine learning models tuned for your false positive tolerance. Ensemble approaches that catch fraud while minimizing legitimate transaction friction." @@ -38,7 +38,7 @@ solutions: description: "From signal generation to execution, we build trading systems that leverage AI for alpha generation while maintaining the reliability trading demands." icon: "chart" - title: "Risk Analytics & Modeling" - description: "Portfolio risk, credit risk, market risk—AI models that quantify and predict risk in real-time, integrated with your existing risk infrastructure." + description: "Portfolio risk, credit risk, market risk: AI models that quantify and predict risk in real-time, integrated with your existing risk infrastructure." icon: "server" - title: "Compliance & RegTech" description: "Automated compliance monitoring, transaction surveillance, and regulatory reporting. AI that helps you stay compliant, not create new risks." @@ -54,7 +54,7 @@ relatedIndustries: - healthcare faqs: - question: "Can you build AI systems that meet regulatory requirements?" - answer: "Yes. We build with compliance in mind from the start—audit trails, model explainability, access controls, and documentation that satisfies regulators. We've shipped systems that passed SOC 2 audits and regulatory reviews." + answer: "Yes. We build with compliance in mind from the start: audit trails, model explainability, access controls, and documentation that satisfies regulators. We've shipped systems that passed SOC 2 audits and regulatory reviews." - question: "How do you achieve sub-100ms latency for AI inference?" answer: "We optimize the entire stack: efficient model architectures, optimized serving infrastructure, strategic caching, and data pipelines designed for real-time processing. Every millisecond is accounted for." - question: "Can you integrate with our existing trading infrastructure?" diff --git a/content/industries/healthcare.mdx b/content/industries/healthcare.mdx index 677a29f..e991d63 100644 --- a/content/industries/healthcare.mdx +++ b/content/industries/healthcare.mdx @@ -2,7 +2,7 @@ title: "Healthcare" tagline: "HIPAA compliant. Clinically validated. Life-saving." description: | - Healthcare AI isn't about flashy demos—it's about improving patient outcomes without creating new risks. We build AI systems that clinicians trust, patients benefit from, and compliance teams approve. HIPAA-compliant from architecture to deployment. + Healthcare AI isn't about flashy demos. It's about improving patient outcomes without creating new risks. We build AI systems that clinicians trust, patients benefit from, and compliance teams approve. HIPAA-compliant from architecture to deployment. heroStats: - value: "2hrs+" label: "Saved per physician daily" @@ -25,7 +25,7 @@ challenges: icon: "users" solutions: - title: "Clinical Documentation AI" - description: "Reduce physician documentation burden with AI that assists with notes, summaries, and EHR entry—without compromising accuracy or compliance." + description: "Reduce physician documentation burden with AI that assists with notes, summaries, and EHR entry, without compromising accuracy or compliance." icon: "document" featured: true - title: "Diagnostic Decision Support" @@ -56,11 +56,11 @@ faqs: - question: "How do you ensure HIPAA compliance?" answer: "We implement the full technical safeguards: encryption, access controls, audit logging, secure data handling, and BAAs with all vendors. Our architects have specific HIPAA experience and we document compliance at every step." - question: "Can AI be trusted for clinical decisions?" - answer: "With appropriate design, yes. We build AI as decision support, not replacement—providing evidence and recommendations while keeping clinicians in control. Transparency and explainability are core requirements." + answer: "With appropriate design, yes. We build AI as decision support, not replacement, providing evidence and recommendations while keeping clinicians in control. Transparency and explainability are core requirements." - question: "How do you handle integration with EHR systems?" answer: "We have experience with Epic, Cerner, and other major EHRs. We work with your IT team to establish secure integration patterns that work within your existing infrastructure." - question: "What about FDA approval for medical AI?" - answer: "For AI that makes clinical claims, FDA clearance may be required. We understand the regulatory landscape and can help you navigate the appropriate pathway—whether that's 510(k), De Novo, or designing to avoid regulatory scope." + answer: "For AI that makes clinical claims, FDA clearance may be required. We understand the regulatory landscape and can help you navigate the appropriate pathway, whether that's 510(k), De Novo, or designing to avoid regulatory scope." cta: title: "Build AI That Improves Patient Care" description: "Talk to engineers who understand healthcare. We'll help you build AI systems that clinicians trust and compliance approves." diff --git a/content/industries/saas.mdx b/content/industries/saas.mdx index 64f03c2..869605a 100644 --- a/content/industries/saas.mdx +++ b/content/industries/saas.mdx @@ -2,7 +2,7 @@ title: "SaaS & Technology" tagline: "Smart features. Faster development. Competitive edge." description: | - Your competitors are adding AI. Your customers are expecting it. We help SaaS companies ship AI features fast—intelligent automation, smart search, AI copilots—without derailing your product roadmap or blowing your infrastructure budget. + Your competitors are adding AI. Your customers are expecting it. We help SaaS companies ship AI features fast: intelligent automation, smart search, AI copilots, without derailing your product roadmap or blowing your infrastructure budget. heroStats: - value: "12 weeks" label: "From concept to production" @@ -56,13 +56,13 @@ faqs: - question: "How do you keep AI costs sustainable?" answer: "We architect for cost from day one: caching strategies, model selection based on task complexity, efficient prompting, and hybrid approaches that use expensive models only when needed. We target AI costs below 10% of feature revenue." - question: "Can you work with our existing engineering team?" - answer: "Yes—that's our model. We embed with your team, work in your codebase, and transfer knowledge as we build. You're not outsourcing; you're augmenting." + answer: "Yes. That's our model. We embed with your team, work in your codebase, and transfer knowledge as we build. You're not outsourcing; you're augmenting." - question: "How long until we have an AI feature in production?" answer: "Most features reach production within 8-12 weeks. We start with a focused scope, ship something real, and iterate based on user feedback." - question: "What about AI reliability for paying customers?" - answer: "We implement extensive testing, output validation, and fallback mechanisms. AI features need to be as reliable as the rest of your product—we engineer for that standard." + answer: "We implement extensive testing, output validation, and fallback mechanisms. AI features need to be as reliable as the rest of your product. We engineer for that standard." cta: - title: "Add AI to Your Product—Fast" + title: "Add AI to Your Product, Fast" description: "Talk to our product AI team. We'll help you identify high-impact AI features and ship them without derailing your roadmap." buttonText: "Schedule a Call" buttonLink: "/contact" diff --git a/content/services/ai-agents.mdx b/content/services/ai-agents.mdx index 0aed5ad..e40cad0 100644 --- a/content/services/ai-agents.mdx +++ b/content/services/ai-agents.mdx @@ -4,10 +4,10 @@ headline: "AI Agents" headlineAccent: "That Get Real Work Done" tagline: "From chatbots to agents that actually get work done." description: | - The next wave of AI isn't about generating text—it's about taking action. We build AI agents that reason through complex tasks, use tools, and execute multi-step workflows autonomously. Production-ready agents that integrate with your systems and handle real business processes. + The next wave of AI isn't about generating text. It's about taking action. We build AI agents that reason through complex tasks, use tools, and execute multi-step workflows autonomously. Production-ready agents that integrate with your systems and handle real business processes. capabilities: - title: "Multi-Step Reasoning & Planning" - description: "Build agents that break down complex goals into actionable steps. Our agents plan, execute, and adapt—handling the nuanced decision-making that simple automation can't touch." + description: "Build agents that break down complex goals into actionable steps. Our agents plan, execute, and adapt, handling the nuanced decision-making that simple automation can't touch." icon: "brain" - title: "Tool Use & API Integration" description: "Connect agents to your existing tools, databases, and APIs. From Salesforce to Slack to custom internal systems, we build agents that work within your ecosystem." @@ -39,18 +39,18 @@ relatedExpertise: - ai-security faqs: - question: "What is the difference between an AI agent and a chatbot?" - answer: "Chatbots respond to queries. Agents take action. An AI agent can research information, update databases, send emails, schedule meetings, and execute multi-step workflows autonomously—not just suggest what you should do." + answer: "Chatbots respond to queries. Agents take action. An AI agent can research information, update databases, send emails, schedule meetings, and execute multi-step workflows autonomously, not just suggest what you should do." - question: "How do you ensure AI agents are safe in production?" answer: "We implement multiple safety layers: action constraints that limit what agents can do, sandboxed execution environments, approval workflows for sensitive actions, comprehensive logging, and rollback capabilities when things go wrong." - question: "Can AI agents work with our legacy systems?" - answer: "Yes. Our engineers specialize in building integration layers that connect modern AI capabilities with existing enterprise systems—even those without modern APIs." + answer: "Yes. Our engineers specialize in building integration layers that connect modern AI capabilities with existing enterprise systems, even those without modern APIs." - question: "How long until we have a working agent?" answer: "Most clients see a working prototype within the first week. Production deployment typically takes 2-4 weeks, depending on the complexity of your workflows and integration requirements." - question: "What kind of tasks are best suited for AI agents?" - answer: "AI agents excel at tasks that are repetitive but require judgment—research and data gathering, document processing, customer inquiry routing, lead qualification, and multi-system workflows. If a task involves multiple steps, uses several tools, and currently requires human decision-making at each stage, it's a strong candidate for an AI agent." + answer: "AI agents excel at tasks that are repetitive but require judgment: research and data gathering, document processing, customer inquiry routing, lead qualification, and multi-system workflows. If a task involves multiple steps, uses several tools, and currently requires human decision-making at each stage, it's a strong candidate for an AI agent." cta: title: "Ready to Deploy AI Agents?" - description: "Talk to our team about automating your complex workflows with AI agents. We'll show you what's possible—and what's production-ready today." + description: "Talk to our team about automating your complex workflows with AI agents. We'll show you what's possible, and what's production-ready today." buttonText: "Schedule a Call" buttonLink: "/contact" seo: diff --git a/content/services/ai-engineering.mdx b/content/services/ai-engineering.mdx index 8eb4d1b..4913c25 100644 --- a/content/services/ai-engineering.mdx +++ b/content/services/ai-engineering.mdx @@ -4,7 +4,7 @@ headline: "Enterprise AI Engineering" headlineAccent: "Production-Ready AI Systems" tagline: "Build, deploy, and scale reliable AI systems." description: | - AI engineering services for teams that need reliable, secure, and scalable AI systems in production — from data pipelines to model deployment and monitoring. + AI engineering services for teams that need reliable, secure, and scalable AI systems in production: from data pipelines to model deployment and monitoring. capabilities: - title: "AI System Architecture" description: "Design scalable AI architectures covering data ingestion, model serving, APIs, and application integration." @@ -19,7 +19,7 @@ capabilities: description: "Implement CI/CD for models, automated evaluation, versioning, monitoring, and rollback strategies." icon: "code" - title: "AI Application Development" - description: "Embed AI into web, mobile, and backend systems — from semantic search to personalized recommendations and real-time decision engines." + description: "Embed AI into web, mobile, and backend systems: from semantic search to personalized recommendations and real-time decision engines." icon: "smartphone" - title: "AI System Monitoring & Optimization" description: "Track model accuracy, latency, cost, drift, and reliability in production environments." @@ -151,6 +151,6 @@ seo: ## Your AI System, Built for Production -Most AI projects fail between prototype and production. We bridge that gap with engineering discipline — reliable data pipelines, observable model serving, and infrastructure that scales with your business. +Most AI projects fail between prototype and production. We bridge that gap with engineering discipline: reliable data pipelines, observable model serving, and infrastructure that scales with your business. **→ [Talk to an AI engineer](/contact-us)** diff --git a/content/services/ai-privacy.mdx b/content/services/ai-privacy.mdx index cbcba5d..7e7e6d0 100644 --- a/content/services/ai-privacy.mdx +++ b/content/services/ai-privacy.mdx @@ -4,7 +4,7 @@ headline: "AI Privacy" headlineAccent: "Without Compromising Performance" tagline: "Protect sensitive data without sacrificing AI capabilities." description: | - AI systems can memorize training data, leak PII in outputs, and send sensitive information to third-party APIs. We build AI applications that protect data privacy by design—meeting compliance requirements while delivering the AI capabilities your business needs. + AI systems can memorize training data, leak PII in outputs, and send sensitive information to third-party APIs. We build AI applications that protect data privacy by design, meeting compliance requirements while delivering the AI capabilities your business needs. capabilities: - title: "Data Leakage Prevention" description: "Implement output scanning, PII detection, and content filtering to prevent sensitive data from appearing in AI responses." @@ -42,7 +42,7 @@ faqs: - question: "How do you prevent AI from exposing PII?" answer: "We implement multiple layers: input sanitization to remove PII before it reaches models, output scanning to catch leaked data, and architectural patterns that minimize PII exposure throughout the system." - question: "What about AI and GDPR data subject rights?" - answer: "We build systems that support right to access, erasure, and portability for data used in AI systems—including mechanisms to track which data influenced model training." + answer: "We build systems that support right to access, erasure, and portability for data used in AI systems, including mechanisms to track which data influenced model training." - question: "Can you make existing AI systems compliant?" answer: "Usually, yes. We audit current systems, identify gaps, and implement technical controls to meet compliance requirements. Some cases require architectural changes, which we can phase in without disrupting operations." cta: @@ -58,6 +58,6 @@ seo: ## Why Choose Procedure for AI Privacy - **Compliance expertise**: We've built HIPAA-compliant and GDPR-ready AI systems -- **Technical depth**: Privacy isn't just policy—we implement the technical controls +- **Technical depth**: Privacy isn't just policy. We implement the technical controls - **Privacy by design**: We architect for privacy from the start, not as a patch - **Pragmatic approach**: We balance privacy requirements with business needs diff --git a/content/services/ai-security.mdx b/content/services/ai-security.mdx index 1472bec..840ec2d 100644 --- a/content/services/ai-security.mdx +++ b/content/services/ai-security.mdx @@ -41,7 +41,7 @@ aiSecurityData: output: "Vulnerability report with severity ratings and fixes" icon: "monitor" - title: "LLM Security Architecture Review" - description: "Security review of your AI system design — before or after launch." + description: "Security review of your AI system design, before or after launch." features: - "Model access control & isolation" - "API security & credential management" @@ -116,15 +116,15 @@ aiSecurityData: - text: "Want theoretical consulting without hands-on work" faqs: - question: "What's the difference between AI security and regular application security?" - answer: "AI systems have unique attack vectors — prompt injection, jailbreaks, data leakage through model outputs, system prompt extraction — that traditional security testing doesn't cover. We specialize in these AI-specific risks." + answer: "AI systems have unique attack vectors, including prompt injection, jailbreaks, data leakage through model outputs, and system prompt extraction, that traditional security testing doesn't cover. We specialize in these AI-specific risks." - question: "Do you only work with companies using OpenAI/ChatGPT?" - answer: "No. We secure systems built on any LLM — OpenAI, Anthropic Claude, open-source models (Llama, Mistral), or custom fine-tuned models. The attack vectors are similar across providers." + answer: "No. We secure systems built on any LLM: OpenAI, Anthropic Claude, open-source models (Llama, Mistral), or custom fine-tuned models. The attack vectors are similar across providers." - question: "How long does an AI security assessment take?" answer: "Most assessments complete in 2-4 weeks depending on scope. A focused red team engagement on a single AI feature can be faster. Full architecture reviews of complex systems take longer." - question: "Do you help with EU AI Act compliance?" answer: "Yes. We assess your AI systems against EU AI Act requirements, help determine risk classification, and document compliance. We also align with ISO/IEC 42001 and NIST AI RMF." - question: "What do we get at the end of an engagement?" - answer: "A detailed report with findings, severity ratings, proof-of-concept demonstrations where applicable, and specific remediation guidance. We don't just find problems — we help you fix them." + answer: "A detailed report with findings, severity ratings, proof-of-concept demonstrations where applicable, and specific remediation guidance. We don't just find problems. We help you fix them." compliance: - "OWASP LLM Top 10" - "NIST AI RMF" @@ -137,7 +137,7 @@ seo: ## Get Started With Procedure -Whether you need AI red teaming, architecture reviews, or ongoing security support — we're here to help. +Whether you need AI red teaming, architecture reviews, or ongoing security support, we're here to help. **→ [Schedule a call with our AI security team](/contact-us)** diff --git a/content/services/backend-development.mdx b/content/services/backend-development.mdx index eabde6b..0ac4f69 100644 --- a/content/services/backend-development.mdx +++ b/content/services/backend-development.mdx @@ -138,7 +138,7 @@ faqs: answer: "Yes. Performance optimization, reliability, and security are integral to our backend development approach." cta: title: "Talk to a Backend Specialist" - description: "If backend failures affect revenue, trust, or growth — engineering quality is non-negotiable. Let's discuss how we can help build reliable backend systems." + description: "If backend failures affect revenue, trust, or growth, engineering quality is non-negotiable. Let's discuss how we can help build reliable backend systems." buttonText: "Schedule a Call" buttonLink: "/contact-us" seo: @@ -148,7 +148,7 @@ seo: ## Get Started With Procedure -Whether you need backend architecture review, production backend development, or system modernization — we're here to help. +Whether you need backend architecture review, production backend development, or system modernization, we're here to help. **→ [Schedule a call with our backend team](/contact-us)** diff --git a/content/services/cloud.mdx b/content/services/cloud.mdx index 8a76545..727b0b4 100644 --- a/content/services/cloud.mdx +++ b/content/services/cloud.mdx @@ -4,7 +4,7 @@ headline: "Cloud Architecture" headlineAccent: "That Scales Without Breaking the Bank" tagline: "AWS. GCP. Azure. Architected right." description: | - Cloud infrastructure should accelerate your business, not slow it down with complexity and cost overruns. We design cloud architectures that scale with your growth, stay secure under attack, and don't break the bank—on AWS, GCP, or Azure. + Cloud infrastructure should accelerate your business, not slow it down with complexity and cost overruns. We design cloud architectures that scale with your growth, stay secure under attack, and don't break the bank, on AWS, GCP, or Azure. capabilities: - title: "Multi-Cloud Architecture" description: "Design resilient systems across cloud providers. Avoid vendor lock-in while leveraging the best of each platform." @@ -19,7 +19,7 @@ capabilities: description: "Architect for uptime. Multi-AZ deployments, automated failover, and disaster recovery that actually works when you need it." icon: "layers" - title: "Infrastructure as Code" - description: "Terraform, Pulumi, CloudFormation—reproducible infrastructure that lives in version control. No more snowflake servers." + description: "Terraform, Pulumi, CloudFormation: reproducible infrastructure that lives in version control. No more snowflake servers." icon: "code" - title: "Migration & Modernization" description: "Move from on-premise to cloud, or from legacy cloud to modern architecture. We handle the migration without disrupting your business." @@ -39,7 +39,7 @@ relatedExpertise: - ai-privacy faqs: - question: "Which cloud provider should we use?" - answer: "It depends on your existing investments, team expertise, and specific workloads. AWS offers the broadest services, GCP excels at data and ML, Azure integrates well with Microsoft ecosystems. We help you choose—or design for multi-cloud when that makes sense." + answer: "It depends on your existing investments, team expertise, and specific workloads. AWS offers the broadest services, GCP excels at data and ML, Azure integrates well with Microsoft ecosystems. We help you choose, or design for multi-cloud when that makes sense." - question: "How do you approach cloud cost optimization?" answer: "We analyze your current usage, right-size resources, implement reserved capacity strategies, and set up continuous cost monitoring. Most clients see 30-50% cost reduction within the first quarter." - question: "Can you help us migrate from on-premise?" @@ -58,7 +58,7 @@ seo: ## Why Choose Procedure for Cloud -- **Cross-cloud expertise**: We're not locked to one vendor—we design for your needs +- **Cross-cloud expertise**: We're not locked to one vendor. We design for your needs - **Cost-conscious**: We optimize for TCO, not just technical elegance - **Production experience**: We've operated infrastructure at scale, not just designed it -- **Security-first**: Cloud security isn't optional—it's foundational +- **Security-first**: Cloud security isn't optional. It's foundational diff --git a/content/services/design-systems.mdx b/content/services/design-systems.mdx index bb006f3..83020e0 100644 --- a/content/services/design-systems.mdx +++ b/content/services/design-systems.mdx @@ -2,9 +2,9 @@ title: "Design Systems" headline: "Design Systems" headlineAccent: "That Scale Across Products" -tagline: "Components, tokens, documentation—done right." +tagline: "Components, tokens, documentation, done right." description: | - A good design system multiplies your team's output. We build design systems that developers love using—well-documented components, consistent tokens, and patterns that make the right thing easy to do. Stop reinventing the wheel on every feature. + A good design system multiplies your team's output. We build design systems that developers love using: well-documented components, consistent tokens, and patterns that make the right thing easy to do. Stop reinventing the wheel on every feature. capabilities: - title: "Design Token Architecture" description: "Define your visual language in code. Colors, typography, spacing, and shadows as tokens that flow from design to implementation." @@ -41,11 +41,11 @@ faqs: - question: "Should we build a design system in-house or use an existing one?" answer: "It depends on your needs. For many products, starting with a base like Radix or shadcn and customizing makes sense. For products with unique branding or complex requirements, a custom system pays off. We help you decide and implement either approach." - question: "How long does it take to build a design system?" - answer: "A foundational system (tokens, core components, basic documentation) can be production-ready in 4-6 weeks. Comprehensive systems take longer, but we structure for incremental value—you can use what we've built while we add more." + answer: "A foundational system (tokens, core components, basic documentation) can be production-ready in 4-6 weeks. Comprehensive systems take longer, but we structure for incremental value. You can use what we've built while we add more." - question: "How do you ensure adoption of the design system?" - answer: "We build for developer experience—good documentation, clear APIs, and components that are genuinely easier to use than building from scratch. We also work with teams during rollout to address feedback and friction." + answer: "We build for developer experience: good documentation, clear APIs, and components that are genuinely easier to use than building from scratch. We also work with teams during rollout to address feedback and friction." - question: "Can you improve an existing design system?" - answer: "Yes. We often help teams level up existing systems—improving accessibility, adding missing components, fixing inconsistencies, or upgrading documentation. We meet you where you are." + answer: "Yes. We often help teams level up existing systems: improving accessibility, adding missing components, fixing inconsistencies, or upgrading documentation. We meet you where you are." cta: title: "Build a Design System That Ships" description: "Talk to our team about your design system needs. Whether starting fresh or improving existing systems, we help you move faster." @@ -58,7 +58,7 @@ seo: ## Why Choose Procedure for Design Systems -- **Engineering quality**: Components built like production code—tested, accessible, performant +- **Engineering quality**: Components built like production code: tested, accessible, performant - **Designer partnership**: We work with your designers to capture intent accurately - **Adoption focus**: We build for adoption, not just technical elegance - **Maintenance-conscious**: Systems designed to evolve without accumulating debt diff --git a/content/services/forward-deployed.mdx b/content/services/forward-deployed.mdx index a6c3ade..90fdf14 100644 --- a/content/services/forward-deployed.mdx +++ b/content/services/forward-deployed.mdx @@ -3,7 +3,7 @@ title: "Forward-Deployed Engineering" headline: "Embedded Engineers That Ship Like They're" headlineAccent: "On Your Payroll" description: | - Forward-deployed engineering puts senior engineers directly inside your organization. They attend your standups, use your tools, and ship production code alongside your team—including AI-powered features. Your team, without the 6-month hiring cycle. + Forward-deployed engineering puts senior engineers directly inside your organization. They attend your standups, use your tools, and ship production code alongside your team, including AI-powered features. Your team, without the 6-month hiring cycle. primaryCTA: text: "Schedule a Strategy Call" href: "/contact-us" @@ -20,7 +20,7 @@ benefits: stat: "100%" statLabel: "Knowledge retention" - title: "Senior Expertise Without the Hiring Bottleneck" - description: "Finding senior engineers takes 6-8 months on average. Our forward-deployed model delivers engineers with deep production experience—now building AI solutions—within 5 business days. Our certified best workplace culture attracts and retains top engineering talent." + description: "Finding senior engineers takes 6-8 months on average. Our forward-deployed model delivers engineers with deep production experience, now building AI solutions, within 5 business days. Our certified best workplace culture attracts and retains top engineering talent." stat: "5 days" statLabel: "Time to deploy" - title: "Flexibility to Scale Up or Down" diff --git a/content/services/frontend-development.mdx b/content/services/frontend-development.mdx index fc571e7..f61df2a 100644 --- a/content/services/frontend-development.mdx +++ b/content/services/frontend-development.mdx @@ -48,7 +48,7 @@ whoWeWorkWith: - icon: "building" title: "Enterprise Organizations" description: "Modernizing complex or legacy frontends while maintaining business continuity." - closingStatement: "Our frontend engineers integrate closely with product, design, and backend teams — operating as owners, not implementers." + closingStatement: "Our frontend engineers integrate closely with product, design, and backend teams, operating as owners, not implementers." process: - number: 1 title: "Product & UX Alignment" @@ -131,14 +131,14 @@ faqs: - question: "Do you work with US-based companies?" answer: "Yes. Procedure works with companies across India and the United States, supporting distributed teams and cross-border product development." - question: "Can you improve an existing frontend codebase?" - answer: "Absolutely. Many engagements start with audits and incremental architectural improvements. We diagnose performance issues, technical debt, and scalability bottlenecks—then fix them systematically." + answer: "Absolutely. Many engagements start with audits and incremental architectural improvements. We diagnose performance issues, technical debt, and scalability bottlenecks, then fix them systematically." - question: "Do you handle frontend SEO and performance optimization?" answer: "Yes. These are core to how we design and build frontends. We optimize rendering strategies, Core Web Vitals, and crawlability as part of our standard development process." - question: "How do frontend development engagements typically work?" - answer: "We offer flexible engagement models based on scope, timelines, and team structure. Whether you need dedicated engineers, project-based delivery, or long-term partnership—we adapt to your workflow." + answer: "We offer flexible engagement models based on scope, timelines, and team structure. Whether you need dedicated engineers, project-based delivery, or long-term partnership, we adapt to your workflow." cta: title: "Talk to a Frontend Specialist" - description: "If frontend performance affects revenue, adoption, or trust — engineering quality matters. Let's discuss how we can help accelerate your frontend development without shortcuts." + description: "If frontend performance affects revenue, adoption, or trust, engineering quality matters. Let's discuss how we can help accelerate your frontend development without shortcuts." buttonText: "Schedule a Call" buttonLink: "/contact-us" seo: @@ -156,7 +156,7 @@ Procedure works with: - Growth-stage companies scaling frontend architecture - Enterprises modernizing complex or legacy frontends -Our frontend engineers integrate closely with product, design, and backend teams — operating as owners, not implementers. +Our frontend engineers integrate closely with product, design, and backend teams, operating as owners, not implementers. --- @@ -194,7 +194,7 @@ This is frontend development engineered for **speed today and scale tomorrow**. ## Frontend Technologies We Work With -We choose frontend technologies based on product context — not trends. +We choose frontend technologies based on product context, not trends. Our frontend development expertise includes: @@ -240,7 +240,7 @@ Our frontend development services support: - **Enterprise web applications** - Complex business logic with intuitive user experiences - **High-traffic, SEO-driven frontends** - Built to handle scale and search visibility -If frontend performance affects revenue, adoption, or trust — engineering quality matters. +If frontend performance affects revenue, adoption, or trust, engineering quality matters. --- @@ -285,7 +285,7 @@ This is frontend development without shortcuts. ## Why Frontend Quality Matters -The frontend is often the first—and only—touchpoint users have with your product. +The frontend is often the first, and only, touchpoint users have with your product. Poor frontend engineering costs you: - **User trust** - Slow, janky interfaces drive users away @@ -303,7 +303,7 @@ Premium frontend development is an investment in: ## Get Started With Procedure -Whether you need dedicated frontend engineers, project-based delivery, or architectural guidance — we're here to help. +Whether you need dedicated frontend engineers, project-based delivery, or architectural guidance, we're here to help. **→ [Schedule a call with our frontend team](/contact-us)** diff --git a/content/services/kubernetes.mdx b/content/services/kubernetes.mdx index 4b65395..4477740 100644 --- a/content/services/kubernetes.mdx +++ b/content/services/kubernetes.mdx @@ -78,7 +78,7 @@ whyChoose: - "Focus on reliability, cost control, and operability" - "Experience across SaaS, AI platforms, and internal systems" - "Clear communication with engineering leadership" - - "Knowledge transfer — no black boxes" + - "Knowledge transfer, no black boxes" outcomes: - value: "Reduced" label: "Infrastructure costs through optimization" @@ -120,7 +120,7 @@ testimonials: quote: "Working with Procedure has been amazing! Their clear communication, smooth project management, and expertise made them feel like part of our team. They built and launched our app in just 12 weeks, helping us reach 1000+ paying users in the first 6 months. We're excited to keep building with them!" faqs: - question: "Do you offer Kubernetes managed services?" - answer: "No. We focus on consulting, architecture, and enablement — helping teams operate Kubernetes themselves with confidence." + answer: "No. We focus on consulting, architecture, and enablement, helping teams operate Kubernetes themselves with confidence." - question: "Which cloud providers do you support?" answer: "We work with Kubernetes across AWS (EKS), GCP (GKE), Azure (AKS), and self-managed environments." - question: "Can you help fix an existing Kubernetes setup?" @@ -141,7 +141,7 @@ seo: ## Get Started With Procedure -Whether you need architecture reviews, hands-on implementation, or ongoing platform support — we're here to help. +Whether you need architecture reviews, hands-on implementation, or ongoing platform support, we're here to help. **→ [Schedule a call with our Kubernetes team](/contact-us)** diff --git a/content/services/mobile-development.mdx b/content/services/mobile-development.mdx index 0e05d60..2fc15e7 100644 --- a/content/services/mobile-development.mdx +++ b/content/services/mobile-development.mdx @@ -141,7 +141,7 @@ seo: ## Get Started With Procedure -Whether you need dedicated mobile teams, project-based development, or ongoing mobile support — we're here to help. +Whether you need dedicated mobile teams, project-based development, or ongoing mobile support, we're here to help. **→ [Schedule a call with our mobile team](/contact-us)** diff --git a/content/services/product-design.mdx b/content/services/product-design.mdx index 009c38e..a74e4ed 100644 --- a/content/services/product-design.mdx +++ b/content/services/product-design.mdx @@ -4,7 +4,7 @@ headline: "Product Design Services" headlineAccent: "Built for Real Products" tagline: "Product design for revenue-critical digital products." description: | - Product design services for product-led teams building usable, scalable, and conversion-focused experiences — from early concepts to production-ready interfaces. + Product design services for product-led teams building usable, scalable, and conversion-focused experiences: from early concepts to production-ready interfaces. capabilities: - title: "Product Discovery & UX Strategy" description: "User research and workflow analysis. Problem definition and opportunity mapping. Experience architecture and user journeys." @@ -131,10 +131,10 @@ faqs: - question: "Do you provide design systems?" answer: "Yes. We design scalable design systems that support long-term product growth and consistency across teams." - question: "Can you help with product strategy?" - answer: "Yes. Design and product strategy are connected — we help define which features to build and how to position them before detailed design." + answer: "Yes. Design and product strategy are connected. We help define which features to build and how to position them before detailed design." cta: title: "Talk to a Product Design Specialist" - description: "If design decisions affect your product's growth, performance, and usability — we can help. Let's design a product that actually ships." + description: "If design decisions affect your product's growth, performance, and usability, we can help. Let's design a product that actually ships." buttonText: "Schedule a Call" buttonLink: "/contact-us" seo: @@ -144,7 +144,7 @@ seo: ## Get Started With Procedure -Whether you need product discovery, UX design, UI design, or design systems — we're here to help. +Whether you need product discovery, UX design, UI design, or design systems, we're here to help. **→ [Schedule a call with our product design team](/contact-us)** diff --git a/content/services/software-testing-and-qa.mdx b/content/services/software-testing-and-qa.mdx index 71f8ffa..aaeb333 100644 --- a/content/services/software-testing-and-qa.mdx +++ b/content/services/software-testing-and-qa.mdx @@ -61,7 +61,7 @@ process: description: "Structured manual testing combined with automation where it delivers long-term leverage." - number: 4 title: "Release Confidence Reporting" - description: "Clear go/no-go signals tied to real product risk — not vanity metrics." + description: "Clear go/no-go signals tied to real product risk, not vanity metrics." useCases: - icon: "layoutDashboard" title: "Embedded QA Team" @@ -121,7 +121,7 @@ testimonials: faqs: - question: "When should a startup invest in QA?" answer: "As soon as real users, revenue, or SLAs are involved. QA prevents costly production failures later." - - question: "Manual testing or automation — which is better?" + - question: "Manual testing or automation, which is better?" answer: "Both. Manual testing uncovers real-world issues; automation protects against regressions at scale. We implement the right balance based on your release cadence and risk profile." - question: "Can QA work with existing frontend and backend teams?" answer: "Yes. Our QA integrates seamlessly with existing frontend and backend development workflows. We embed with your teams and contribute to your release process." @@ -131,7 +131,7 @@ faqs: answer: "Yes. QA strategy, tooling, and coverage evolve as your product and team mature. We adapt our approach to match your growth stage and release velocity." cta: title: "Talk to a QA Specialist" - description: "If your team ships often and reliability matters, QA becomes a growth enabler — not a bottleneck. Let's discuss how we can help protect your product quality." + description: "If your team ships often and reliability matters, QA becomes a growth enabler, not a bottleneck. Let's discuss how we can help protect your product quality." buttonText: "Schedule a Call" buttonLink: "/contact-us" seo: @@ -141,7 +141,7 @@ seo: ## Get Started With Procedure -Whether you need embedded QA engineers, release-based testing, or automation frameworks — we're here to help. +Whether you need embedded QA engineers, release-based testing, or automation frameworks, we're here to help. **→ [Schedule a call with our QA team](/contact-us)** diff --git a/content/technologies/dotnet.mdx b/content/technologies/dotnet.mdx index dbc9c3c..c3f8fe9 100644 --- a/content/technologies/dotnet.mdx +++ b/content/technologies/dotnet.mdx @@ -2,13 +2,13 @@ title: ".NET Development Services" headline: "Custom .NET Development Services" headlineAccent: "for Mission-Critical Systems" -description: "Production-grade .NET applications that scale, integrate cleanly, and stay maintainable for years. Certified engineers who work as your team—not a detached vendor." +description: "Production-grade .NET applications that scale, integrate cleanly, and stay maintainable for years. Certified engineers who work as your team, not a detached vendor." capabilities: - title: "Custom .NET Application Development" description: "Enterprise-grade web applications, APIs, and backend systems using ASP.NET Core, C#, and Entity Framework. Architected for security and long-term maintainability." icon: "api" - title: ".NET Modernization & Migration" - description: "Migrate from .NET Framework 4.x to .NET 8 without production downtime. Incremental strategies—strangler fig, containerization—to reduce risk while unlocking modern performance." + description: "Migrate from .NET Framework 4.x to .NET 8 without production downtime. Incremental strategies, including strangler fig and containerization, to reduce risk while unlocking modern performance." icon: "workflow" - title: ".NET Microservices Architecture" description: "Distributed .NET systems with clear service boundaries, independent deployments, and built-in resilience. Monolith decomposition done right." @@ -67,14 +67,14 @@ whoWeWorkWith: bullets: - "Strong typing and compile-time safety matter for complex domain logic" - "Performance requirements demand a runtime that competes with Go and Rust" - - "Your team values mature tooling—Visual Studio, Rider, robust debugging" + - "Your team values mature tooling: Visual Studio, Rider, robust debugging" - "LTS releases align with your maintenance and upgrade cycles" - icon: "target" title: "Product Leaders & Platform Owners" subtitle: ".NET is strategic when:" bullets: - "Building internal platforms that need to outlast individual team tenures" - - "Backward compatibility matters—.NET's migration path is predictable" + - "Backward compatibility matters: .NET's migration path is predictable" - "You need enterprise integrations (Active Directory, SQL Server, Dynamics)" - "Multiple deployment targets: cloud, on-prem, hybrid, edge" commonApplications: @@ -97,18 +97,18 @@ philosophy: subtitle: "We approach .NET development as long-term system engineering, not short-term delivery. Every decision is made with production reality, system ownership, and future evolution in mind." blocks: - title: "Product Thinking Over Task Execution" - description: "We design .NET systems around business workflows, operational constraints, and real usage patterns—not feature lists or time-based delivery. The goal is systems that work in practice, not just on paper." + description: "We design .NET systems around business workflows, operational constraints, and real usage patterns, not feature lists or time-based delivery. The goal is systems that work in practice, not just on paper." - title: "Ownership Is the Default" - description: "Every .NET system is built so internal teams can understand, operate, and extend it independently. Clear architecture decisions, documentation, and test coverage are treated as core deliverables—not optional extras." + description: "Every .NET system is built so internal teams can understand, operate, and extend it independently. Clear architecture decisions, documentation, and test coverage are treated as core deliverables, not optional extras." - title: "A High, Non-Negotiable Quality Bar" description: "Quality is not a phase. Code health, testability, and maintainability are enforced consistently so .NET systems remain reliable as they grow in complexity and usage." - title: "Designed for Long-Term Evolution" description: "We build .NET systems to evolve over years, not sprints. Architecture choices favor clarity, extensibility, and predictable change over short-term convenience." - title: "Intentional Technical Debt Management" - description: "Trade-offs are made consciously, documented clearly, and revisited deliberately. Technical debt is managed as a strategic decision—not an accident that compounds over time." + description: "Trade-offs are made consciously, documented clearly, and revisited deliberately. Technical debt is managed as a strategic decision, not an accident that compounds over time." architecture: title: "How We Architect .NET Applications" - subtitle: "Clean Architecture principles—business logic independent of frameworks, databases, and delivery mechanisms. When .NET 10 arrives or you swap databases, your core code doesn't change." + subtitle: "Clean Architecture principles: business logic independent of frameworks, databases, and delivery mechanisms. When .NET 10 arrives or you swap databases, your core code doesn't change." layers: - name: "Domain Layer" description: "Encapsulates core business rules and domain models in stable logic, isolated from frameworks and infrastructure." @@ -125,7 +125,7 @@ testimonials: quote: "Modernized our legacy .NET platform while feature delivery continued. The team handled risk thoughtfully and operated like senior engineers embedded in our organization." engagementModels: title: ".NET Engagement Models" - subtitle: "Choose the model that fits your project. All engagements start with discovery—no long-term commitment required." + subtitle: "Choose the model that fits your project. All engagements start with discovery, no long-term commitment required." models: - title: "Dedicated .NET Team" description: "Full-time engineers as an extension of your organization. Shared accountability for outcomes." @@ -137,7 +137,7 @@ engagementModels: description: "Targeted expertise: architecture reviews, migration planning, performance audits." bestFor: "Technical due diligence, pre-investment validation" - title: "Ongoing .NET Product Ownership" - description: "Full responsibility for your .NET product—development, maintenance, operations." + description: "Full responsibility for your .NET product: development, maintenance, operations." bestFor: "Non-technical founders, teams focused on business growth" riskReversal: title: "Why Teams Choose Us for .NET Projects" @@ -172,17 +172,17 @@ faqs: - question: "How long does .NET development take?" answer: "Timelines depend on complexity. Simple APIs take 4–6 weeks. MVPs typically take 8–12 weeks. Full enterprise applications require 4–8 months for initial release. Legacy modernization projects span 3–12 months depending on system size. We work in sprints with continuous releases so you see progress early." - question: "Do you offer .NET staff augmentation?" - answer: "Yes. Senior .NET engineers who integrate with your team—your repos, your processes, your standups. This works well when you have technical leadership but need capacity. For teams needing technical direction, a dedicated team model is usually a better fit." + answer: "Yes. Senior .NET engineers who integrate with your team: your repos, your processes, your standups. This works well when you have technical leadership but need capacity. For teams needing technical direction, a dedicated team model is usually a better fit." - question: "What industries have you built .NET systems for?" answer: "Financial services (payment processing, trading, regulatory reporting), healthcare (patient portals, claims, HIPAA-compliant systems), SaaS (multi-tenant platforms, subscription billing), and enterprise (internal tools, workflow automation, ERP integrations). Our engineers adapt quickly to new domains." - question: "How do you compare to other .NET development companies?" - answer: "We're not the largest or cheapest. What's different: senior engineers only—no juniors learning on your project. Ownership mindset—outcomes, not just features. Transparent communication—you always know what's happening. No lock-in—you own everything, easy to leave. US + India presence—timezone coverage and cost efficiency." + answer: "We're not the largest or cheapest. What's different: senior engineers only, no juniors learning on your project. Ownership mindset, outcomes, not just features. Transparent communication, you always know what's happening. No lock-in, you own everything, easy to leave. US + India presence, timezone coverage and cost efficiency." - question: "Is .NET suitable for enterprise and mission-critical systems?" answer: "Yes. .NET is widely adopted for enterprise applications due to its strong type system, high-throughput runtime, and long-term Microsoft support (LTS releases supported 3+ years). The ecosystem includes mature libraries for security, data access, and enterprise integration. Organizations like Stack Overflow and major financial institutions run core systems on .NET." - question: "Can modern .NET applications scale with growing demand?" answer: "Yes. Modern .NET is designed for both horizontal and vertical scaling. ASP.NET Core handles high request volumes with minimal overhead through async-first architecture. The platform supports microservices patterns, container orchestration, and distributed systems. Performance benchmarks place .NET among the fastest web frameworks available." - question: "Do you work with existing or legacy .NET systems?" - answer: "Yes. Much of our work involves existing systems—modernizing .NET Framework applications, refactoring monoliths, or migrating to modern runtimes. We use incremental approaches like strangler fig patterns so teams continue shipping features while modernization happens in parallel, without large-scale rewrites." + answer: "Yes. Much of our work involves existing systems: modernizing .NET Framework applications, refactoring monoliths, or migrating to modern runtimes. We use incremental approaches like strangler fig patterns so teams continue shipping features while modernization happens in parallel, without large-scale rewrites." - question: "How risky is migrating from .NET Framework to modern .NET?" answer: "What reduces risk: Microsoft's .NET Upgrade Assistant automates mechanical work. Incremental strategies (strangler fig) let you migrate piece by piece. Side-by-side deployment allows old and new to coexist. What increases risk: heavy Windows-specific APIs (WCF, legacy WinForms), tightly coupled architecture, and missing tests (we often write tests first). Most migrations complete in 3–6 months without production incidents." - question: "Is .NET suitable for cloud-native and cross-platform applications?" @@ -193,7 +193,7 @@ faqs: answer: "When systems become business-critical and architectural decisions carry long-term consequences. When modernization is needed but internal teams lack bandwidth. When previous development left fragile code needing stabilization. Or when stakeholders need independent validation before committing resources." cta: title: "Ready to Discuss Your .NET Development Services Project?" - description: "Talk directly with engineers—not sales. We'll assess fit and give honest next steps." + description: "Talk directly with engineers, not sales. We'll assess fit and give honest next steps." buttonText: "Request a .NET Architecture Review" buttonLink: "/contact-us" supportingNote: "No obligation. No pressure. Clear technical direction." diff --git a/content/use-cases/ai-search.mdx b/content/use-cases/ai-search.mdx index c5639b0..5cbfa08 100644 --- a/content/use-cases/ai-search.mdx +++ b/content/use-cases/ai-search.mdx @@ -3,7 +3,7 @@ title: "Search That" heroHighlight: "Understands What Users Mean" tagline: "Beyond keywords. True understanding." description: | - Traditional search fails when users don't know the right words. Semantic search understands intent—finding relevant results even when queries don't match exact keywords. We build search systems that surface what users actually need, dramatically improving discovery and conversion. + Traditional search fails when users don't know the right words. Semantic search understands intent, finding relevant results even when queries don't match exact keywords. We build search systems that surface what users actually need, dramatically improving discovery and conversion. problemSolution: before: - "Users abandon search after finding nothing relevant" @@ -78,13 +78,13 @@ industries: - financial-services faqs: - question: "How is semantic search different from Elasticsearch?" - answer: 'Elasticsearch (and similar) match keywords. Semantic search matches meaning—understanding that "running shoes" and "jogging sneakers" are the same concept. We often combine both: keyword precision with semantic understanding.' + answer: 'Elasticsearch (and similar) match keywords. Semantic search matches meaning, understanding that "running shoes" and "jogging sneakers" are the same concept. We often combine both: keyword precision with semantic understanding.' - question: "What vector database should we use?" answer: "It depends on your scale, latency requirements, and infrastructure preferences. Pinecone for managed simplicity, Weaviate for flexibility, pgvector if you're already on Postgres. We help you choose and implement the right option." - question: "How long does semantic search take to implement?" answer: "A production-ready semantic search system typically takes 4-8 weeks. We can have a working prototype in your data within the first week." - question: "Can you improve our existing search?" - answer: "Yes. We often augment existing search with semantic capabilities—adding vector search alongside keyword matching for better results without replacing your current infrastructure." + answer: "Yes. We often augment existing search with semantic capabilities, adding vector search alongside keyword matching for better results without replacing your current infrastructure." cta: title: "Build Search That Converts" description: "Talk to our search engineers. We'll show you how semantic search can improve discovery and drive business results." diff --git a/content/use-cases/conversational-ai.mdx b/content/use-cases/conversational-ai.mdx index 90f3907..ac36530 100644 --- a/content/use-cases/conversational-ai.mdx +++ b/content/use-cases/conversational-ai.mdx @@ -3,7 +3,7 @@ title: "Conversations That" heroHighlight: "Actually Solve Problems" tagline: "Beyond scripted responses. Real resolution." description: | - Chatbots have a reputation problem—because most chatbots are frustrating dead ends. We build conversational AI that understands context, takes action, and resolves issues. LLM-powered assistants that customers prefer to waiting on hold. + Chatbots have a reputation problem, because most chatbots are frustrating dead ends. We build conversational AI that understands context, takes action, and resolves issues. LLM-powered assistants that customers prefer to waiting on hold. problemSolution: before: - "Chatbots frustrate users with circular conversations" @@ -46,7 +46,7 @@ features: description: "Connect to your systems to take action: CRMs, order management, ticketing, scheduling. Resolution, not just responses." - icon: "phone" title: "Omnichannel Deployment" - description: "Deploy across web, mobile, SMS, WhatsApp, Slack—wherever your users are. Consistent experience across channels." + description: "Deploy across web, mobile, SMS, WhatsApp, Slack, wherever your users are. Consistent experience across channels." - icon: "userGroup" title: "Smart Escalation" description: "Know when to bring in humans. Smooth handoff with conversation history and context for agents." @@ -79,11 +79,11 @@ industries: - saas faqs: - question: "How is LLM-powered conversational AI different from traditional chatbots?" - answer: "Traditional chatbots follow decision trees and keyword matching—they break when users deviate from expected inputs. LLM-powered systems understand natural language, handle variations, and generate contextual responses. The experience is dramatically more natural and effective." + answer: "Traditional chatbots follow decision trees and keyword matching. They break when users deviate from expected inputs. LLM-powered systems understand natural language, handle variations, and generate contextual responses. The experience is dramatically more natural and effective." - question: "How do you prevent the AI from saying something wrong?" answer: "We implement multiple layers: system prompts that establish boundaries, output filtering for problematic content, guardrails that limit what the AI can claim or promise, and escalation triggers for sensitive topics. Plus comprehensive logging to catch and fix issues." - question: "Can conversational AI integrate with our existing systems?" - answer: "Yes—that's essential for resolution. We build integrations with CRMs, ticketing systems, order management, and custom backends. The AI can look up information and take actions, not just provide canned responses." + answer: "Yes. That's essential for resolution. We build integrations with CRMs, ticketing systems, order management, and custom backends. The AI can look up information and take actions, not just provide canned responses." - question: "How long until we have a working chatbot?" answer: "A production-ready conversational AI typically takes 6-10 weeks, depending on integration complexity. We start with core capabilities and expand based on real conversation data." cta: diff --git a/content/use-cases/document-ai.mdx b/content/use-cases/document-ai.mdx index 573a84e..e4e1749 100644 --- a/content/use-cases/document-ai.mdx +++ b/content/use-cases/document-ai.mdx @@ -3,7 +3,7 @@ title: "Turn Documents Into" heroHighlight: "Actionable Data" tagline: "Extract. Classify. Analyze. At scale." description: | - Your organization runs on documents—contracts, invoices, reports, applications. We build AI systems that read, understand, and extract structured data from documents at scale. Stop manual data entry. Start making decisions from document insights. + Your organization runs on documents: contracts, invoices, reports, applications. We build AI systems that read, understand, and extract structured data from documents at scale. Stop manual data entry. Start making decisions from document insights. problemSolution: before: - "Manual document review bottlenecks operations" diff --git a/lib/case-studies-data.ts b/lib/case-studies-data.ts index 4c67535..2269219 100644 --- a/lib/case-studies-data.ts +++ b/lib/case-studies-data.ts @@ -56,7 +56,7 @@ export const caseStudies: CaseStudy[] = [ serviceType: "AI Engineering", title: "AI-Powered Search That Increased Revenue by $180M Annually", description: - "A leading online retailer struggled with search relevance—customers were abandoning searches and leaving the site. We rebuilt their search infrastructure with semantic understanding and real-time personalization, transforming their highest-traffic feature into their highest-converting one.", + "A leading online retailer struggled with search relevance. Customers were abandoning searches and leaving the site. We rebuilt their search infrastructure with semantic understanding and real-time personalization, transforming their highest-traffic feature into their highest-converting one.", metrics: [ { value: "34%", label: "Higher conversion rate" }, { value: "$180M", label: "Additional annual revenue" }, @@ -107,7 +107,7 @@ export const caseStudies: CaseStudy[] = [ serviceType: "Product Engineering", title: "Platform Modernization That Enabled 10x Scale", description: - "A fast-growing tech company hit a wall—their monolithic architecture could not handle increasing load and slowed development to a crawl. Our engineers led a strategic microservices transformation that unlocked both technical scalability and team velocity.", + "A fast-growing tech company hit a wall. Their monolithic architecture could not handle increasing load and slowed development to a crawl. Our engineers led a strategic microservices transformation that unlocked both technical scalability and team velocity.", metrics: [ { value: "10x", label: "Traffic capacity increase" }, { value: "3x", label: "Faster deployment cycles" }, diff --git a/lib/expertise-data.tsx b/lib/expertise-data.tsx index 096bb69..bffd834 100644 --- a/lib/expertise-data.tsx +++ b/lib/expertise-data.tsx @@ -460,7 +460,7 @@ export const expertisePages: Record = { headlineAccent: "Actually Work", tagline: "From prototype to production in days, not months.", description: - "Most LLM demos fail in production. Hallucinations, latency issues, and security gaps derail enterprise deployments. We build LLM applications engineered for real-world reliability—with RAG architectures, guardrails, and observability baked in from day one.", + "Most LLM demos fail in production. Hallucinations, latency issues, and security gaps derail enterprise deployments. We build LLM applications engineered for real-world reliability: RAG architectures, guardrails, and observability baked in from day one.", }, capabilities: [ { @@ -514,7 +514,7 @@ export const expertisePages: Record = { "Production experience: We've shipped LLM apps handling millions of queries, not just demos", "Speed to value: First working prototype in 5 days, not 5 months of exploration", "Full-stack capability: From infrastructure to UI, we build the complete solution", - "Model-agnostic: OpenAI, Anthropic, open-source—we use what works best for your use case", + "Model-agnostic: OpenAI, Anthropic, open-source. We use what works best for your use case", ], cta: { headline: "Ready to Ship Your LLM Application?", @@ -561,14 +561,14 @@ export const expertisePages: Record = { headlineAccent: "Execute, Not Just Recommend", tagline: "From chatbots to agents that actually get work done.", description: - "The next wave of AI isn't about generating text—it's about taking action. We build AI agents that reason through complex tasks, use tools, and execute multi-step workflows autonomously. Production-ready agents that integrate with your systems and handle real business processes.", + "The next wave of AI isn't about generating text. It's about taking action. We build AI agents that reason through complex tasks, use tools, and execute multi-step workflows autonomously. Production-ready agents that integrate with your systems and handle real business processes.", }, capabilities: [ { icon: "brain", title: "Multi-Step Reasoning & Planning", description: - "Build agents that break down complex goals into actionable steps. Our agents plan, execute, and adapt—handling the nuanced decision-making that simple automation can't touch.", + "Build agents that break down complex goals into actionable steps. Our agents plan, execute, and adapt, handling the nuanced decision-making that simple automation can't touch.", }, { icon: "puzzle", @@ -620,13 +620,13 @@ export const expertisePages: Record = { cta: { headline: "Ready to Deploy AI Agents?", description: - "Talk to our team about automating your complex workflows with AI agents. We'll show you what's possible—and what's production-ready today.", + "Talk to our team about automating your complex workflows with AI agents. We'll show you what's possible, and what's production-ready today.", }, faqs: [ { question: "What's the difference between an AI agent and a chatbot?", answer: - "Chatbots respond to queries. Agents take action. An AI agent can research information, update databases, send emails, schedule meetings, and execute multi-step workflows autonomously—not just suggest what you should do.", + "Chatbots respond to queries. Agents take action. An AI agent can research information, update databases, send emails, schedule meetings, and execute multi-step workflows autonomously, not just suggest what you should do.", }, { question: "How do you ensure AI agents are safe in production?", @@ -636,7 +636,7 @@ export const expertisePages: Record = { { question: "Can AI agents work with our legacy systems?", answer: - "Yes. Our engineers specialize in building integration layers that connect modern AI capabilities with existing enterprise systems—even those without modern APIs.", + "Yes. Our engineers specialize in building integration layers that connect modern AI capabilities with existing enterprise systems, even those without modern APIs.", }, { question: "How long until we have a working agent?", @@ -659,9 +659,9 @@ export const expertisePages: Record = { badge: "AI Security", headline: "Secure AI Systems From", headlineAccent: "Architecture to Production", - tagline: "LLM security isn't an afterthought—it's foundational.", + tagline: "LLM security isn't an afterthought. It's foundational.", description: - "Prompt injection. Jailbreaks. Data exfiltration. The attack surface for AI systems is different from traditional software—and most teams aren't prepared. We build AI security into your systems from the ground up, protecting against both known threats and emerging attack vectors.", + "Prompt injection. Jailbreaks. Data exfiltration. The attack surface for AI systems is different from traditional software, and most teams aren't prepared. We build AI security into your systems from the ground up, protecting against both known threats and emerging attack vectors.", }, capabilities: [ { @@ -725,7 +725,7 @@ export const expertisePages: Record = { { question: "What is prompt injection and why should I care?", answer: - "Prompt injection is when attackers craft inputs that manipulate your LLM into ignoring its instructions. It can lead to data leakage, unauthorized actions, and reputation damage. It's the SQL injection of the AI era—and just as dangerous.", + "Prompt injection is when attackers craft inputs that manipulate your LLM into ignoring its instructions. It can lead to data leakage, unauthorized actions, and reputation damage. It's the SQL injection of the AI era, and just as dangerous.", }, { question: @@ -761,7 +761,7 @@ export const expertisePages: Record = { headlineAccent: "Doesn't Compromise Results", tagline: "Protect sensitive data without sacrificing AI capabilities.", description: - "AI systems can memorize training data, leak PII in outputs, and send sensitive information to third-party APIs. We build AI applications that protect data privacy by design—meeting compliance requirements while delivering the AI capabilities your business needs.", + "AI systems can memorize training data, leak PII in outputs, and send sensitive information to third-party APIs. We build AI applications that protect data privacy by design, meeting compliance requirements while delivering the AI capabilities your business needs.", }, capabilities: [ { @@ -812,7 +812,7 @@ export const expertisePages: Record = { ], whyProcedure: [ "Compliance expertise: We've built HIPAA-compliant and GDPR-ready AI systems", - "Technical depth: Privacy isn't just policy—we implement the technical controls", + "Technical depth: Privacy isn't just policy. We implement the technical controls", "Privacy by design: We architect for privacy from the start, not as a patch", "Pragmatic approach: We balance privacy requirements with business needs", ], @@ -835,7 +835,7 @@ export const expertisePages: Record = { { question: "What about AI and GDPR data subject rights?", answer: - "We build systems that support right to access, erasure, and portability for data used in AI systems—including mechanisms to track which data influenced model training.", + "We build systems that support right to access, erasure, and portability for data used in AI systems, including mechanisms to track which data influenced model training.", }, { question: "Can you make existing AI systems compliant?", @@ -860,7 +860,7 @@ export const expertisePages: Record = { headlineAccent: "Users Love", tagline: "Beautiful interfaces. Blazing performance. Built to last.", description: - "Great products need great interfaces. We build modern web applications using React, Next.js, and Vue—with attention to performance, accessibility, and user experience. Senior frontend engineers who've shipped products used by millions, now embedded with your team.", + "Great products need great interfaces. We build modern web applications using React, Next.js, and Vue, with attention to performance, accessibility, and user experience. Senior frontend engineers who've shipped products used by millions, now embedded with your team.", }, capabilities: [ { @@ -879,7 +879,7 @@ export const expertisePages: Record = { icon: "bolt", title: "Performance Optimization", description: - "Core Web Vitals aren't just metrics—they're revenue. We optimize load times, interactivity, and visual stability for real business impact.", + "Core Web Vitals aren't just metrics. They're revenue. We optimize load times, interactivity, and visual stability for real business impact.", }, { icon: "palette", @@ -891,7 +891,7 @@ export const expertisePages: Record = { icon: "accessibility", title: "Accessibility Engineering", description: - "WCAG compliance isn't optional. We build interfaces that work for everyone—screen readers, keyboard navigation, and assistive technology.", + "WCAG compliance isn't optional. We build interfaces that work for everyone: screen readers, keyboard navigation, and assistive technology.", }, { icon: "workflow", @@ -925,7 +925,7 @@ export const expertisePages: Record = { { question: "Do you work with our existing codebase?", answer: - "Yes. Our engineers embed with your team and work in your codebase. We can join an existing project or start something new—either way, we follow your conventions and contribute to your codebase.", + "Yes. Our engineers embed with your team and work in your codebase. We can join an existing project or start something new. Either way, we follow your conventions and contribute to your codebase.", }, { question: "How do you handle design handoff?", @@ -940,7 +940,7 @@ export const expertisePages: Record = { { question: "Can you help with performance issues?", answer: - "Absolutely. We regularly diagnose and fix performance problems in existing applications—slow load times, janky interactions, bundle size issues. We measure improvements with real metrics.", + "Absolutely. We regularly diagnose and fix performance problems in existing applications: slow load times, janky interactions, bundle size issues. We measure improvements with real metrics.", }, ], relatedExpertise: ["backend", "design-systems", "product-design"], @@ -960,14 +960,14 @@ export const expertisePages: Record = { headlineAccent: "Built for Growth", tagline: "Infrastructure that won't hold you back.", description: - "Your backend is the foundation everything else builds on. We engineer robust, scalable systems using Node.js, Python, and Go—designed for the traffic you'll have tomorrow, not just today. Cloud-native architectures that grow with your business.", + "Your backend is the foundation everything else builds on. We engineer robust, scalable systems using Node.js, Python, and Go, designed for the traffic you'll have tomorrow, not just today. Cloud-native architectures that grow with your business.", }, capabilities: [ { icon: "api", title: "API Design & Development", description: - "Build APIs that developers love. REST, GraphQL, gRPC—we choose the right approach for your use case and implement it with production-grade reliability.", + "Build APIs that developers love. REST, GraphQL, gRPC. We choose the right approach for your use case and implement it with production-grade reliability.", }, { icon: "layers", @@ -979,13 +979,13 @@ export const expertisePages: Record = { icon: "workflow", title: "Data Pipeline Engineering", description: - "Build pipelines that process data reliably at scale. Kafka, Spark, Airflow—the tools change, but our engineering principles produce systems that work.", + "Build pipelines that process data reliably at scale. Kafka, Spark, Airflow. The tools change, but our engineering principles produce systems that work.", }, { icon: "database", title: "Database Design & Optimization", description: - "Choose the right database, design the schema, and optimize for your query patterns. PostgreSQL, MongoDB, Redis, and the rest—we know when to use what.", + "Choose the right database, design the schema, and optimize for your query patterns. PostgreSQL, MongoDB, Redis, and the rest. We know when to use what.", }, { icon: "lock", @@ -1011,9 +1011,9 @@ export const expertisePages: Record = { "GraphQL", ], whyProcedure: [ - "Production veterans: We've run systems at scale—millions of requests, complex data pipelines", + "Production veterans: We've run systems at scale: millions of requests, complex data pipelines", "Polyglot pragmatism: We use the right language for the job, not the trendy one", - "Cloud-native experience: AWS, GCP, Azure—we build for modern infrastructure", + "Cloud-native experience: AWS, GCP, Azure. We build for modern infrastructure", "Operational mindset: We think about how systems fail, not just how they succeed", ], cta: { @@ -1025,12 +1025,12 @@ export const expertisePages: Record = { { question: "Which backend language should we use?", answer: - "It depends. Node.js for JavaScript-ecosystem teams and I/O-heavy services. Python for data-intensive applications and ML integration. Go for performance-critical services. We help you choose—and we're fluent in all three.", + "It depends. Node.js for JavaScript-ecosystem teams and I/O-heavy services. Python for data-intensive applications and ML integration. Go for performance-critical services. We help you choose, and we're fluent in all three.", }, { question: "Can you help with our existing backend?", answer: - "Yes. We work with existing codebases regularly—adding features, improving performance, and evolving architecture. We embed with your team and contribute to your codebase.", + "Yes. We work with existing codebases regularly: adding features, improving performance, and evolving architecture. We embed with your team and contribute to your codebase.", }, { question: "How do you approach testing for backend systems?", @@ -1040,7 +1040,7 @@ export const expertisePages: Record = { { question: "Do you handle DevOps as well?", answer: - "We're not just writing code—we can set up CI/CD, containerization, and cloud infrastructure. Our backend engineers understand the full stack from development to production.", + "We're not just writing code. We can set up CI/CD, containerization, and cloud infrastructure. Our backend engineers understand the full stack from development to production.", }, ], relatedExpertise: ["frontend", "cloud", "kubernetes"], @@ -1060,7 +1060,7 @@ export const expertisePages: Record = { headlineAccent: "Across Every Platform", tagline: "iOS. Android. React Native. Built right.", description: - "Mobile users expect native-quality experiences—smooth animations, instant responsiveness, and offline capability. We build mobile applications that meet those expectations, whether native iOS, Android, or cross-platform with React Native.", + "Mobile users expect native-quality experiences: smooth animations, instant responsiveness, and offline capability. We build mobile applications that meet those expectations, whether native iOS, Android, or cross-platform with React Native.", }, capabilities: [ { @@ -1079,7 +1079,7 @@ export const expertisePages: Record = { icon: "code", title: "React Native Development", description: - "When you need to move fast across platforms, React Native delivers. We build React Native apps that feel native—because we know both the framework and the platforms beneath it.", + "When you need to move fast across platforms, React Native delivers. We build React Native apps that feel native, because we know both the framework and the platforms beneath it.", }, { icon: "database", @@ -1112,7 +1112,7 @@ export const expertisePages: Record = { ], whyProcedure: [ "Platform depth: Engineers who understand iOS and Android at the system level", - "Cross-platform pragmatism: We recommend React Native when it makes sense—not always", + "Cross-platform pragmatism: We recommend React Native when it makes sense, not always", "Performance obsession: Mobile users notice every dropped frame", "Launch experience: We've shipped apps to millions of users", ], @@ -1123,7 +1123,7 @@ export const expertisePages: Record = { }, faqs: [ { - question: "Native or React Native—which should we choose?", + question: "Native or React Native: which should we choose?", answer: "If you're building a platform-defining experience or need deep hardware integration, go native. For most B2B apps and MVPs, React Native offers faster development with acceptable tradeoffs. We help you make the right choice for your specific situation.", }, @@ -1160,14 +1160,14 @@ export const expertisePages: Record = { headlineAccent: "Ships Confidence", tagline: "Automated testing. CI/CD. Zero regressions.", description: - "Shipping fast doesn't mean shipping broken. We build quality engineering practices into your development process—automated testing, CI/CD pipelines, and the systems that catch bugs before users do. Ship with confidence, not crossed fingers.", + "Shipping fast doesn't mean shipping broken. We build quality engineering practices into your development process: automated testing, CI/CD pipelines, and the systems that catch bugs before users do. Ship with confidence, not crossed fingers.", }, capabilities: [ { icon: "document", title: "Test Strategy & Architecture", description: - "Design a testing approach that fits your system. Unit tests, integration tests, end-to-end tests—the right mix for your architecture and risk profile.", + "Design a testing approach that fits your system. Unit tests, integration tests, end-to-end tests. The right mix for your architecture and risk profile.", }, { icon: "check", @@ -1212,7 +1212,7 @@ export const expertisePages: Record = { ], whyProcedure: [ "Engineering-first QA: We write code, not just test cases", - "Automation focus: Manual testing doesn't scale—we build automated systems", + "Automation focus: Manual testing doesn't scale. We build automated systems", "Production insight: QA informed by production observability and real user behavior", "Process integration: We embed QA into your development workflow, not as a separate step", ], @@ -1230,7 +1230,7 @@ export const expertisePages: Record = { { question: "What testing tools do you use?", answer: - "We use what works for your stack—Jest, Playwright, Cypress, pytest, JUnit, and many others. The specific tools matter less than the testing patterns and infrastructure we build around them.", + "We use what works for your stack: Jest, Playwright, Cypress, pytest, JUnit, and many others. The specific tools matter less than the testing patterns and infrastructure we build around them.", }, { question: "How do you handle flaky tests?", @@ -1240,7 +1240,7 @@ export const expertisePages: Record = { { question: "Can you help with performance testing?", answer: - "Yes. We design load testing strategies, implement performance test suites, and integrate performance monitoring into your CI/CD pipeline. Performance isn't just QA—it's continuous engineering.", + "Yes. We design load testing strategies, implement performance test suites, and integrate performance monitoring into your CI/CD pipeline. Performance isn't just QA. It's continuous engineering.", }, ], relatedExpertise: ["backend", "frontend", "mobile"], @@ -1260,7 +1260,7 @@ export const expertisePages: Record = { headlineAccent: "Scales With You", tagline: "AWS. GCP. Azure. Architected right.", description: - "Cloud infrastructure should accelerate your business, not slow it down with complexity and cost overruns. We design cloud architectures that scale with your growth, stay secure under attack, and don't break the bank—on AWS, GCP, or Azure.", + "Cloud infrastructure should accelerate your business, not slow it down with complexity and cost overruns. We design cloud architectures that scale with your growth, stay secure under attack, and don't break the bank, on AWS, GCP, or Azure.", }, capabilities: [ { @@ -1291,7 +1291,7 @@ export const expertisePages: Record = { icon: "code", title: "Infrastructure as Code", description: - "Terraform, Pulumi, CloudFormation—reproducible infrastructure that lives in version control. No more snowflake servers.", + "Terraform, Pulumi, CloudFormation: reproducible infrastructure that lives in version control. No more snowflake servers.", }, { icon: "workflow", @@ -1311,10 +1311,10 @@ export const expertisePages: Record = { "PagerDuty", ], whyProcedure: [ - "Cross-cloud expertise: We're not locked to one vendor—we design for your needs", + "Cross-cloud expertise: We're not locked to one vendor. We design for your needs", "Cost-conscious: We optimize for TCO, not just technical elegance", "Production experience: We've operated infrastructure at scale, not just designed it", - "Security-first: Cloud security isn't optional—it's foundational", + "Security-first: Cloud security isn't optional. It's foundational", ], cta: { headline: "Architect Your Cloud Right", @@ -1325,7 +1325,7 @@ export const expertisePages: Record = { { question: "Which cloud provider should we use?", answer: - "It depends on your existing investments, team expertise, and specific workloads. AWS offers the broadest services, GCP excels at data and ML, Azure integrates well with Microsoft ecosystems. We help you choose—or design for multi-cloud when that makes sense.", + "It depends on your existing investments, team expertise, and specific workloads. AWS offers the broadest services, GCP excels at data and ML, Azure integrates well with Microsoft ecosystems. We help you choose, or design for multi-cloud when that makes sense.", }, { question: "How do you approach cloud cost optimization?", @@ -1360,14 +1360,14 @@ export const expertisePages: Record = { headlineAccent: "Production-Grade", tagline: "Kubernetes complexity, handled.", description: - "Kubernetes is powerful—and complex. We help you run containers in production without getting lost in YAML files and obscure failure modes. From initial deployment to day-2 operations, we make Kubernetes work for your team instead of against it.", + "Kubernetes is powerful, and complex. We help you run containers in production without getting lost in YAML files and obscure failure modes. From initial deployment to day-2 operations, we make Kubernetes work for your team instead of against it.", }, capabilities: [ { icon: "cube", title: "Cluster Design & Deployment", description: - "Design Kubernetes clusters sized for your workloads. EKS, GKE, AKS, or self-managed—we deploy clusters you can actually operate.", + "Design Kubernetes clusters sized for your workloads. EKS, GKE, AKS, or self-managed. We deploy clusters you can actually operate.", }, { icon: "layers", @@ -1385,7 +1385,7 @@ export const expertisePages: Record = { icon: "globe", title: "Service Mesh Implementation", description: - "Istio, Linkerd, or simpler solutions—we implement service mesh when it adds value, and avoid it when it's overhead.", + "Istio, Linkerd, or simpler solutions. We implement service mesh when it adds value, and avoid it when it's overhead.", }, { icon: "chart", @@ -1397,7 +1397,7 @@ export const expertisePages: Record = { icon: "shield", title: "Security & Compliance", description: - "Pod security, network policies, RBAC, and secrets management. Secure Kubernetes isn't optional—we build it in from the start.", + "Pod security, network policies, RBAC, and secrets management. Secure Kubernetes isn't optional. We build it in from the start.", }, ], technologies: [ @@ -1413,7 +1413,7 @@ export const expertisePages: Record = { whyProcedure: [ "Production operators: We've run Kubernetes at scale, not just deployed it", "Pragmatic adoption: We implement what you need, not every CNCF project", - "Day-2 focus: Deployment is easy—we focus on long-term operations", + "Day-2 focus: Deployment is easy. We focus on long-term operations", "Knowledge transfer: We train your team to operate what we build", ], cta: { @@ -1426,12 +1426,12 @@ export const expertisePages: Record = { question: "Should we use managed Kubernetes (EKS/GKE/AKS) or self-managed?", answer: - "For most teams, managed Kubernetes reduces operational burden and makes sense. We recommend self-managed only when you have specific requirements that managed services can't meet—and the team to support it.", + "For most teams, managed Kubernetes reduces operational burden and makes sense. We recommend self-managed only when you have specific requirements that managed services can't meet, and the team to support it.", }, { question: "How do you handle Kubernetes complexity?", answer: - "We establish clear patterns, automate repetitive tasks, and document decisions. Most Kubernetes complexity comes from over-engineering—we build what you need, not what's technically impressive.", + "We establish clear patterns, automate repetitive tasks, and document decisions. Most Kubernetes complexity comes from over-engineering. We build what you need, not what's technically impressive.", }, { question: "Can you help with an existing Kubernetes setup?", @@ -1461,7 +1461,7 @@ export const expertisePages: Record = { headlineAccent: "AI-Powered Products", tagline: "Make AI usable. Make AI delightful.", description: - "AI capabilities mean nothing if users can't use them. We design AI products that feel intuitive—where the AI enhances the experience instead of creating confusion. Human-centered design that bridges the gap between powerful technology and real user needs.", + "AI capabilities mean nothing if users can't use them. We design AI products that feel intuitive, where the AI enhances the experience instead of creating confusion. Human-centered design that bridges the gap between powerful technology and real user needs.", }, capabilities: [ { @@ -1474,7 +1474,7 @@ export const expertisePages: Record = { icon: "users", title: "User Research & Testing", description: - "Understand how users interact with AI. Research methods adapted for AI products—testing not just interfaces, but the mental models users bring.", + "Understand how users interact with AI. Research methods adapted for AI products: testing not just interfaces, but the mental models users bring.", }, { icon: "bolt", @@ -1513,7 +1513,7 @@ export const expertisePages: Record = { ], whyProcedure: [ "AI-native designers: We understand how AI works, not just how to make things pretty", - "Engineer partnership: Our designers work directly with engineers—no lost-in-translation", + "Engineer partnership: Our designers work directly with engineers. No lost-in-translation", "Research-driven: We design based on user research, not assumptions", "Full-service: From research to prototypes to production assets", ], @@ -1527,7 +1527,7 @@ export const expertisePages: Record = { question: "How is designing for AI different from regular product design?", answer: - "AI introduces uncertainty—outputs vary, latency is unpredictable, and users need to calibrate trust. We design patterns that handle these challenges: loading states for variable latency, confidence indicators, and fallback paths when AI fails.", + "AI introduces uncertainty: outputs vary, latency is unpredictable, and users need to calibrate trust. We design patterns that handle these challenges: loading states for variable latency, confidence indicators, and fallback paths when AI fails.", }, { question: "Do you work with our existing design team?", @@ -1542,7 +1542,7 @@ export const expertisePages: Record = { { question: "Can you help define the AI product strategy?", answer: - "Yes. Design and product strategy are connected—we help you figure out which AI capabilities to build and how to position them before jumping into detailed design.", + "Yes. Design and product strategy are connected. We help you figure out which AI capabilities to build and how to position them before jumping into detailed design.", }, ], relatedExpertise: ["design-systems", "frontend", "llm-applications"], @@ -1560,9 +1560,9 @@ export const expertisePages: Record = { badge: "Design Systems", headline: "Scalable Design Systems That", headlineAccent: "Accelerate Teams", - tagline: "Components, tokens, documentation—done right.", + tagline: "Components, tokens, documentation. Done right.", description: - "A good design system multiplies your team's output. We build design systems that developers love using—well-documented components, consistent tokens, and patterns that make the right thing easy to do. Stop reinventing the wheel on every feature.", + "A good design system multiplies your team's output. We build design systems that developers love using: well-documented components, consistent tokens, and patterns that make the right thing easy to do. Stop reinventing the wheel on every feature.", }, capabilities: [ { @@ -1613,7 +1613,7 @@ export const expertisePages: Record = { "shadcn/ui", ], whyProcedure: [ - "Engineering quality: Components built like production code—tested, accessible, performant", + "Engineering quality: Components built like production code: tested, accessible, performant", "Designer partnership: We work with your designers to capture intent accurately", "Adoption focus: We build for adoption, not just technical elegance", "Maintenance-conscious: Systems designed to evolve without accumulating debt", @@ -1633,17 +1633,17 @@ export const expertisePages: Record = { { question: "How long does it take to build a design system?", answer: - "A foundational system (tokens, core components, basic documentation) can be production-ready in 4-6 weeks. Comprehensive systems take longer, but we structure for incremental value—you can use what we've built while we add more.", + "A foundational system (tokens, core components, basic documentation) can be production-ready in 4-6 weeks. Comprehensive systems take longer, but we structure for incremental value. You can use what we've built while we add more.", }, { question: "How do you ensure adoption of the design system?", answer: - "We build for developer experience—good documentation, clear APIs, and components that are genuinely easier to use than building from scratch. We also work with teams during rollout to address feedback and friction.", + "We build for developer experience: good documentation, clear APIs, and components that are genuinely easier to use than building from scratch. We also work with teams during rollout to address feedback and friction.", }, { question: "Can you improve an existing design system?", answer: - "Yes. We often help teams level up existing systems—improving accessibility, adding missing components, fixing inconsistencies, or upgrading documentation. We meet you where you are.", + "Yes. We often help teams level up existing systems: improving accessibility, adding missing components, fixing inconsistencies, or upgrading documentation. We meet you where you are.", }, ], relatedExpertise: ["product-design", "frontend", "mobile"], diff --git a/lib/industries-data.tsx b/lib/industries-data.tsx index f6d7723..568d85d 100644 --- a/lib/industries-data.tsx +++ b/lib/industries-data.tsx @@ -372,7 +372,7 @@ export const industryPages: Record = { headlineAccent: "Speed of Markets", tagline: "Sub-100ms. SOC 2 compliant. Production-ready.", description: - "Financial markets don't wait. Your AI systems shouldn't either. We build AI applications engineered for the demands of finance—real-time processing, bulletproof reliability, and the compliance posture your regulators expect. From trading signals to fraud detection, we ship production AI in days.", + "Financial markets don't wait. Your AI systems shouldn't either. We build AI applications engineered for the demands of finance: real-time processing, bulletproof reliability, and the compliance posture your regulators expect. From trading signals to fraud detection, we ship production AI in days.", stats: [ { value: "$47M+", label: "fraud prevented for clients" }, { value: "<50ms", label: "average inference latency" }, @@ -410,14 +410,14 @@ export const industryPages: Record = { icon: "bolt", title: "Real-Time ML Infrastructure", description: - "We build inference pipelines optimized for latency—model serving, feature stores, and data pipelines that deliver predictions in milliseconds, not seconds.", + "We build inference pipelines optimized for latency: model serving, feature stores, and data pipelines that deliver predictions in milliseconds, not seconds.", featured: true, }, { icon: "document", title: "Regulatory-Ready Architecture", description: - "Audit logs, model versioning, decision explainability—compliance requirements built into the architecture, not bolted on after.", + "Audit logs, model versioning, decision explainability. Compliance requirements built into the architecture, not bolted on after.", }, { icon: "shield", @@ -435,7 +435,7 @@ export const industryPages: Record = { icon: "server", title: "Risk Analytics & Modeling", description: - "Portfolio risk, credit risk, market risk—AI models that quantify and predict risk in real-time, integrated with your existing risk infrastructure.", + "Portfolio risk, credit risk, market risk: AI models that quantify and predict risk in real-time, integrated with your existing risk infrastructure.", }, { icon: "clipboard", @@ -487,7 +487,7 @@ export const industryPages: Record = { { question: "Can you build AI systems that meet regulatory requirements?", answer: - "Yes. We build with compliance in mind from the start—audit trails, model explainability, access controls, and documentation that satisfies regulators. We've shipped systems that passed SOC 2 audits and regulatory reviews.", + "Yes. We build with compliance in mind from the start: audit trails, model explainability, access controls, and documentation that satisfies regulators. We've shipped systems that passed SOC 2 audits and regulatory reviews.", }, { question: "How do you achieve sub-100ms latency for AI inference?", @@ -520,7 +520,7 @@ export const industryPages: Record = { headlineAccent: "Puts Patients First", tagline: "HIPAA compliant. Clinically validated. Life-saving.", description: - "Healthcare AI isn't about flashy demos—it's about improving patient outcomes without creating new risks. We build AI systems that clinicians trust, patients benefit from, and compliance teams approve. HIPAA-compliant from architecture to deployment.", + "Healthcare AI isn't about flashy demos. It's about improving patient outcomes without creating new risks. We build AI systems that clinicians trust, patients benefit from, and compliance teams approve. HIPAA-compliant from architecture to deployment.", stats: [ { value: "2hrs+", label: "saved per physician daily" }, { value: "98.7%", label: "diagnostic accuracy achieved" }, @@ -558,7 +558,7 @@ export const industryPages: Record = { icon: "document", title: "Clinical Documentation AI", description: - "Reduce physician documentation burden with AI that assists with notes, summaries, and EHR entry—without compromising accuracy or compliance.", + "Reduce physician documentation burden with AI that assists with notes, summaries, and EHR entry, without compromising accuracy or compliance.", featured: true, }, { @@ -636,7 +636,7 @@ export const industryPages: Record = { { question: "Can AI be trusted for clinical decisions?", answer: - "With appropriate design, yes. We build AI as decision support, not replacement—providing evidence and recommendations while keeping clinicians in control. Transparency and explainability are core requirements.", + "With appropriate design, yes. We build AI as decision support, not replacement, providing evidence and recommendations while keeping clinicians in control. Transparency and explainability are core requirements.", }, { question: "How do you handle integration with EHR systems?", @@ -646,7 +646,7 @@ export const industryPages: Record = { { question: "What about FDA approval for medical AI?", answer: - "For AI that makes clinical claims, FDA clearance may be required. We understand the regulatory landscape and can help you navigate the appropriate pathway—whether that's 510(k), De Novo, or designing to avoid regulatory scope.", + "For AI that makes clinical claims, FDA clearance may be required. We understand the regulatory landscape and can help you navigate the appropriate pathway: whether that's 510(k), De Novo, or designing to avoid regulatory scope.", }, ], }, @@ -664,7 +664,7 @@ export const industryPages: Record = { headlineAccent: "Transforms How We Learn", tagline: "Personalized. Accessible. Effective.", description: - "Every learner is different—but most educational software treats them the same. We build AI that adapts to individual learners, generates engaging content, and measures what actually matters: learning outcomes. Education technology that works for students, not just administrators.", + "Every learner is different, but most educational software treats them the same. We build AI that adapts to individual learners, generates engaging content, and measures what actually matters: learning outcomes. Education technology that works for students, not just administrators.", stats: [ { value: "45%", label: "improvement in learning outcomes" }, { value: "3x", label: "faster content creation" }, @@ -676,7 +676,7 @@ export const industryPages: Record = { icon: "users", title: "One Size Doesn't Fit All", description: - "Traditional courseware delivers the same content to every student. But learners have different backgrounds, paces, and styles—AI should adapt to them.", + "Traditional courseware delivers the same content to every student. But learners have different backgrounds, paces, and styles. AI should adapt to them.", }, { icon: "document", @@ -715,13 +715,13 @@ export const industryPages: Record = { icon: "lightbulb", title: "Intelligent Tutoring Systems", description: - "Build AI tutors that provide personalized guidance—Socratic questioning, worked examples, and feedback tailored to each learner.", + "Build AI tutors that provide personalized guidance: Socratic questioning, worked examples, and feedback tailored to each learner.", }, { icon: "clipboard", title: "Automated Assessment & Feedback", description: - "Grade essays, evaluate code, and assess complex work with AI—providing rapid, consistent feedback that helps students improve.", + "Grade essays, evaluate code, and assess complex work with AI, providing rapid, consistent feedback that helps students improve.", }, { icon: "chart", @@ -764,7 +764,7 @@ export const industryPages: Record = { "Learning science informed: We build on research about how people actually learn", "Accessibility commitment: Inclusive design from the start, not an afterthought", "Scale experience: We've built platforms serving millions of learners", - "Outcome focus: We measure what matters—learning gains, not just usage", + "Outcome focus: We measure what matters: learning gains, not just usage", ], cta: { headline: "Build Education AI That Works", @@ -775,17 +775,17 @@ export const industryPages: Record = { { question: "How does adaptive learning AI actually work?", answer: - "We model learner knowledge state based on their interactions—questions answered, time spent, patterns of errors. The AI uses this model to select optimal next content: easier material to reinforce foundations, or harder challenges when ready to advance.", + "We model learner knowledge state based on their interactions: questions answered, time spent, patterns of errors. The AI uses this model to select optimal next content: easier material to reinforce foundations, or harder challenges when ready to advance.", }, { question: "Can AI really grade essays and complex work?", answer: - "For many assessment types, yes—with appropriate human oversight. AI can provide consistent initial evaluation and detailed feedback. We design rubrics and validation processes that maintain assessment quality.", + "For many assessment types, yes, with appropriate human oversight. AI can provide consistent initial evaluation and detailed feedback. We design rubrics and validation processes that maintain assessment quality.", }, { question: "How do you ensure accessibility?", answer: - "Accessibility is a design requirement from day one—not a retrofit. We follow WCAG guidelines, test with assistive technology, and involve users with disabilities in our design process.", + "Accessibility is a design requirement from day one, not a retrofit. We follow WCAG guidelines, test with assistive technology, and involve users with disabilities in our design process.", }, { question: "What about student data privacy (FERPA/COPPA)?", @@ -808,7 +808,7 @@ export const industryPages: Record = { headlineAccent: "Customers Actually Want", tagline: "Smart features. Faster development. Competitive edge.", description: - "Your competitors are adding AI. Your customers are expecting it. We help SaaS companies ship AI features fast—intelligent automation, smart search, AI copilots—without derailing your product roadmap or blowing your infrastructure budget.", + "Your competitors are adding AI. Your customers are expecting it. We help SaaS companies ship AI features fast: intelligent automation, smart search, AI copilots, without derailing your product roadmap or blowing your infrastructure budget.", stats: [ { value: "12 weeks", label: "from concept to production" }, { value: "40%", label: "feature adoption driven by AI" }, @@ -915,7 +915,7 @@ export const industryPages: Record = { "Full-stack capability: From infrastructure to UI, we build complete features", ], cta: { - headline: "Add AI to Your Product—Fast", + headline: "Add AI to Your Product, Fast", description: "Talk to our product AI team. We'll help you identify high-impact AI features and ship them without derailing your roadmap.", }, @@ -928,7 +928,7 @@ export const industryPages: Record = { { question: "Can you work with our existing engineering team?", answer: - "Yes—that's our model. We embed with your team, work in your codebase, and transfer knowledge as we build. You're not outsourcing; you're augmenting.", + "Yes. That's our model. We embed with your team, work in your codebase, and transfer knowledge as we build. You're not outsourcing; you're augmenting.", }, { question: "How long until we have an AI feature in production?", @@ -938,7 +938,7 @@ export const industryPages: Record = { { question: "What about AI reliability for paying customers?", answer: - "We implement extensive testing, output validation, and fallback mechanisms. AI features need to be as reliable as the rest of your product—we engineer for that standard.", + "We implement extensive testing, output validation, and fallback mechanisms. AI features need to be as reliable as the rest of your product. We engineer for that standard.", }, ], }, From 5cbd11992afcf69fb20ceaf34359d238716d3acc Mon Sep 17 00:00:00 2001 From: vibemarketerpromax Date: Thu, 12 Feb 2026 16:57:59 +0530 Subject: [PATCH 3/3] fix: Remove em dashes from terms pages and RiskReversal component --- app/policies/terms-conditions/page.tsx | 12 ++++++------ app/terms/page.tsx | 12 ++++++------ components/expertise/RiskReversal.tsx | 2 +- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/app/policies/terms-conditions/page.tsx b/app/policies/terms-conditions/page.tsx index bc4114c..b482b1a 100644 --- a/app/policies/terms-conditions/page.tsx +++ b/app/policies/terms-conditions/page.tsx @@ -74,13 +74,13 @@ export default function TermsConditionsPage() { By accessing, browsing, or using the Procedure website and any of our services, you're agreeing to be bound by these Terms & Conditions and our Privacy Policy. Think of it as a digital - handshake—you're saying "yes" to playing by our + handshake - you're saying "yes" to playing by our rules.

If you don't agree with these terms, that's totally - fine—just don't use our site. + fine -just don't use our site. {" "} We'd appreciate a quick email to{" "}

- All the content we create—including text, images, videos, logos, - and software—belongs to Procedure and is protected by Indian and + All the content we create -including text, images, videos, logos, + and software -belongs to Procedure and is protected by Indian and international intellectual property laws. You can use our content for personal, non-commercial purposes, but please don't copy, redistribute, or create derivative works @@ -617,8 +617,8 @@ export default function TermsConditionsPage() { By Procedure

- We may suspend or end your account or access—without prior - notice—if we believe you've: + We may suspend or end your account or access -without prior + notice -if we believe you've: