diff --git a/public/sitemap.xml b/public/sitemap.xml index 78ea867..46e71a4 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -15,6 +15,31 @@ monthly 0.9 + + https://workroot.in/services/custom-erp-development/ + monthly + 0.8 + + + https://workroot.in/services/university-erp/ + monthly + 0.8 + + + https://workroot.in/services/government-it-solutions-gem-vendor/ + monthly + 0.8 + + + https://workroot.in/services/police-management-system/ + monthly + 0.8 + + + https://workroot.in/services/react-native-app-development/ + monthly + 0.8 + https://workroot.in/portfolio/ weekly diff --git a/src/components/ServiceFaq.astro b/src/components/ServiceFaq.astro new file mode 100644 index 0000000..e30cdc4 --- /dev/null +++ b/src/components/ServiceFaq.astro @@ -0,0 +1,160 @@ +--- +// ServiceFaq — reusable, prop-driven FAQ accordion for the keyword-focused +// service landing pages (e.g. /services/custom-erp-development). +// +// IMPORTANT: this component renders only the VISIBLE accordion. It does NOT +// emit FAQPage JSON-LD. The owning page is expected to pass the same `faqs` +// array into , which emits exactly one FAQPage node. Keeping +// schema emission in SEO.astro (and out of here) guarantees a single FAQPage +// per page even when several of these accordions could theoretically render. +// +// Visual + a11y behaviour mirrors HomepageFaq.astro (single-open accordion, +// real +
+
+

+ {item.answer} +

+
+
+ + )) + } + + +

+ Have a different question?{' '} + + Ask us directly → + +

+ + + + + + + diff --git a/src/pages/services.astro b/src/pages/services.astro index d7b77cf..a127efb 100644 --- a/src/pages/services.astro +++ b/src/pages/services.astro @@ -246,6 +246,23 @@ const caseStudies = [ }, ]; +// Dedicated, keyword-focused landing pages that deep-dive a service. Keyed by +// the service `id` so each detail section can surface its related page(s) +// directly in the on-page navigation flow. +const landingPages: Record = { + 'government-systems': [ + { label: 'Government IT & GeM vendor', href: '/services/government-it-solutions-gem-vendor' }, + { label: 'Police Management System', href: '/services/police-management-system' }, + ], + 'erp-solutions': [ + { label: 'Custom ERP development', href: '/services/custom-erp-development' }, + { label: 'University ERP', href: '/services/university-erp' }, + ], + 'mobile-development': [ + { label: 'React Native app development', href: '/services/react-native-app-development' }, + ], +}; + // Process steps const processSteps = [ { @@ -545,6 +562,28 @@ const processSteps = [ + + {/* Deep-dive landing pages related to this service */} + {landingPages[service.id] && ( +
+

Explore in depth

+ +
+ )} diff --git a/src/pages/services/custom-erp-development.astro b/src/pages/services/custom-erp-development.astro new file mode 100644 index 0000000..5e595ef --- /dev/null +++ b/src/pages/services/custom-erp-development.astro @@ -0,0 +1,307 @@ +--- +// Custom ERP Development — keyword-focused service landing page. +// Reuses the shared section components (GuaranteeBand, InlineLeadForm, +// ServiceFaq) and feeds Service + FAQ schema into SEO.astro. +// +// All company stats mirror the canonical site-wide set used in +// ProofNumbers.astro, /portfolio, and SEO.astro — 20+ projects · 11 districts · +// 50,000+ records · 99.9% uptime · 8+ years. Case-study numbers are taken +// verbatim from the IIT Patna and Bihar government case studies on /portfolio. +import BaseLayout from '../../layouts/BaseLayout.astro'; +import SEO from '../../components/SEO.astro'; +import GuaranteeBand from '../../components/GuaranteeBand.astro'; +import InlineLeadForm from '../../components/InlineLeadForm.astro'; +import ServiceFaq from '../../components/ServiceFaq.astro'; + +const pageTitle = 'Custom ERP Development Services'; +const pageDescription = + 'Custom ERP development by WorkRoot — bespoke enterprise systems on Spring Boot, Angular & Next.js. Already running for IIT Patna and across 11 government districts. Get a free scope.'; + +const serviceName = 'Custom ERP Development'; +const serviceDescription = + 'Bespoke ERP and enterprise resource planning systems built around your real workflows — modules for operations, personnel, finance, inventory, reporting and role-based access. Delivered with Spring Boot, Angular, and Next.js, and proven in university and multi-district government deployments.'; + +// Capabilities — what a WorkRoot custom ERP build typically covers. +const modules = [ + { title: 'Operations & workflow', body: 'Model your real approval chains, hand-offs, and SLAs instead of bending the business to a rigid template.' }, + { title: 'Role-based access control', body: 'Granular permissions per role, department, and district — the same RBAC layer running in our government deployments.' }, + { title: 'Personnel & HR', body: 'Staff records, duty rosters, leave, and audit trails — the backbone of our 15,000+ officer police deployment.' }, + { title: 'Inventory & assets', body: 'Stock, procurement, and asset lifecycle tracking with reconciliation and low-stock alerting.' }, + { title: 'Dashboards & reporting', body: 'Real-time operational dashboards and scheduled exports for leadership oversight and compliance.' }, + { title: 'Integrations & APIs', body: 'Clean REST APIs so your ERP talks to payment gateways, SMS/email, and existing legacy systems.' }, +]; + +// Comparison table — off-the-shelf ERP vs a WorkRoot custom build. +const comparison = [ + { dimension: 'Fit to your workflow', offShelf: 'You adapt your process to the software', custom: 'The software is built around your process' }, + { dimension: 'Per-seat licensing', offShelf: 'Recurring per-user fees that scale with headcount', custom: 'You own the source — no per-seat tax' }, + { dimension: 'Source-code ownership', offShelf: 'Vendor-locked, closed source', custom: 'Full IP transfer on delivery' }, + { dimension: 'Customisation', offShelf: 'Limited to vendor-exposed settings', custom: 'Any module, any rule, any report' }, + { dimension: 'Data residency', offShelf: 'Often the vendor’s cloud / region', custom: 'Your servers, your region, your control' }, + { dimension: 'Hosting model', offShelf: 'SaaS only', custom: 'On-prem, your VPC, or managed by us' }, +]; + +const stats = [ + { value: '5+', label: 'ERP & enterprise deployments' }, + { value: '20,000+', label: 'Users across systems' }, + { value: '11', label: 'Districts running our platforms' }, + { value: '99.9%', label: 'Uptime on critical systems' }, +]; + +const faqs = [ + { + question: 'How much does a custom ERP cost?', + answer: + 'Custom ERP engagements typically run ₹2,00,000–₹15,00,000 depending on the number of modules, user roles, and integrations. We offer fixed-price quotes for well-defined scopes and time-and-materials for evolving ones. Every estimate is free and itemised.', + }, + { + question: 'How long does it take to build a custom ERP?', + answer: + 'Most ERP builds ship a usable first module in 6–8 weeks and reach full rollout in 3–6 months. We work in 2-week sprints with a live staging environment from day one, so you see and steer working software early rather than waiting for a big-bang launch.', + }, + { + question: 'Do we own the source code?', + answer: + 'Yes. Full IP transfer is included — you receive the repositories, deployment access, and documentation on delivery. There are no per-seat licence fees, and you are free to host, extend, or hand the system to another team at any time.', + }, + { + question: 'Can you integrate with our existing systems?', + answer: + 'Yes. We build clean REST APIs and have integrated ERPs with payment gateways, SMS and email providers, government identity systems, and legacy MySQL/PostgreSQL databases. If your current tool can export data, we can migrate and connect to it.', + }, + { + question: 'Is a custom ERP secure enough for sensitive data?', + answer: + 'Security is built into every layer: role-based access control, encrypted data at rest and in transit, full audit logging, and OWASP-aligned reviews. The same architecture currently runs a Bihar government police platform across 11 districts under strict security compliance.', + }, + { + question: 'What technology stack do you use for ERP?', + answer: + 'We build on Spring Boot for the backend, Angular or Next.js for the admin and user interfaces, and PostgreSQL or MySQL for the data layer — the same stack behind the IIT Patna University Management System and our multi-district government deployments.', + }, +]; +--- + + + + + +
+ +
+
+ + + + ERP & Enterprise Systems + +

+ Custom ERP development that fits + your workflow, not a template. +

+

+ Replace scattered spreadsheets and disconnected tools with one bespoke system your team actually trusts — + built on Spring Boot, Angular, and Next.js, and already running for IIT Patna and across 11 government districts. +

+ +
+ + +
+ {stats.map((stat) => ( +
+

{stat.value}

+

{stat.label}

+
+ ))} +
+
+
+ + +
+
+
+ What we build +

Enterprise software shaped around how you actually operate

+
+

+ An off-the-shelf ERP forces every organisation into the same boxes. That works until your approval chain, your + district structure, or your compliance rules don’t fit the template — and then you are paying per seat for software + your team quietly works around in spreadsheets. A custom ERP flips that relationship: the system is built around the + way you already run, so adoption is high and the workarounds disappear. +

+

+ WorkRoot has been delivering bespoke enterprise systems since 2022, and the engineers on our team carry 8+ years of + experience building software that has to stay up. We have shipped enterprise platforms for an IIT, for a state + government across 11 districts, and for private operators handling tens of thousands of users. Across those systems + we manage 50,000+ records and hold 99.9% uptime on the deployments that cannot + afford to go dark. +

+

+ Every engagement starts with your workflow, not our codebase. We map the real process — who requests what, who + approves it, where it gets stuck — and then build modules that remove the friction: operations and workflow, + role-based access, personnel and HR, inventory and assets, finance, and the dashboards leadership needs to see it + all. The result is one system of record instead of five disconnected tools, and a single source of truth your + auditors will thank you for. +

+

+ Because the system is yours, there are no per-seat licence fees and no vendor lock-in. We hand over the full source + code, the repositories, the deployment pipeline, and the documentation. You can host it on-premise, in your own + cloud account, or let us run it for you under a maintenance retainer — the choice stays with you. +

+
+
+
+
+ + +
+
+
+

Modules we build into custom ERPs

+

Mix and match the pieces your operation needs — each one production-proven in a live deployment.

+
+
+ {modules.map((m) => ( +
+ +

{m.title}

+

{m.body}

+
+ ))} +
+
+
+ + +
+
+
+
+

Off-the-shelf ERP vs a custom build

+

Where a bespoke system pays you back.

+
+
+ + + + + + + + + + + {comparison.map((row, i) => ( + + + + + + ))} + +
Comparison of off-the-shelf ERP software versus a custom ERP built by WorkRoot
DimensionOff-the-shelf ERPCustom ERP (WorkRoot)
{row.dimension}{row.offShelf} + + + {row.custom} + +
+
+
+
+
+ + +
+
+
+ Case study · Enterprise ERP +

University Management System — IIT Patna

+

+ IIT Patna needed a single platform to replace fragmented legacy systems across admissions, course registration, + examination scheduling, grade management, and faculty administration. We built an end-to-end ERP on a + Next.js front end with a Spring Boot backend + and a MySQL data layer — designed for scalability and high availability across the + entire academic community. +

+
+ {[{ v: '3,000+', l: 'Students served' }, { v: '500+', l: 'Courses managed' }, { v: '200+', l: 'Faculty onboarded' }].map((s) => ( +
+

{s.v}

+

{s.l}

+
+ ))} +
+
+ “WorkRoot delivered our University Management System for IIT Patna on time and within budget. The Next.js + Spring Boot + architecture is robust and scalable. They are a reliable technology partner for complex enterprise projects.” +
— Dilip Raj, Director, MOC Soft Technologies Pvt Ltd
+
+ +
+
+
+ + +
+ +
+ + + + + +
diff --git a/src/pages/services/government-it-solutions-gem-vendor.astro b/src/pages/services/government-it-solutions-gem-vendor.astro new file mode 100644 index 0000000..042464c --- /dev/null +++ b/src/pages/services/government-it-solutions-gem-vendor.astro @@ -0,0 +1,307 @@ +--- +// Government IT Solutions / GeM Vendor — keyword-focused service landing page. +// Reuses GuaranteeBand, InlineLeadForm and ServiceFaq, and feeds Service + FAQ +// schema into SEO.astro. +// +// Canonical stats mirror ProofNumbers.astro / /portfolio / SEO.astro: +// 20+ projects · 11 districts · 50,000+ records · 99.9% uptime · 8+ years. +import BaseLayout from '../../layouts/BaseLayout.astro'; +import SEO from '../../components/SEO.astro'; +import GuaranteeBand from '../../components/GuaranteeBand.astro'; +import InlineLeadForm from '../../components/InlineLeadForm.astro'; +import ServiceFaq from '../../components/ServiceFaq.astro'; + +const pageTitle = 'Government IT Solutions & GeM Vendor'; +const pageDescription = + 'GeM-empanelled government IT vendor. WorkRoot builds secure, multi-district public-service platforms — live across 11 Bihar districts at 99.9% uptime. Get a free scope for your tender.'; + +const serviceName = 'Government IT Solutions'; +const serviceDescription = + 'Secure, compliant government IT systems for public bodies and smart-city missions — multi-district deployment, role-based access, audit logging, and data residency. Delivered by a GeM-empanelled vendor with live platforms across 11 districts in Bihar at 99.9% uptime.'; + +const capabilities = [ + { title: 'Multi-district deployment', body: 'One platform rolled out across districts without rewriting it for each — proven across 11 Bihar districts.' }, + { title: 'Citizen-facing portals', body: 'Public service portals for bookings, applications, and status tracking, built for low-bandwidth access.' }, + { title: 'Audit & compliance', body: 'Audit logging baked into the data layer, role-based access control, and tamper-evident record-keeping.' }, + { title: 'Smart-city systems (SCMS)', body: 'Operational systems for civic facilities — slot booking, real-time availability, and oversight dashboards.' }, + { title: 'Data residency & security', body: 'Hosting in your region under strict security standards — encrypted at rest and in transit.' }, + { title: 'High availability', body: 'Infrastructure engineered for 99.9% uptime on mission-critical public services.' }, +]; + +// Capability / readiness stat block presented as a checklist table. +const readiness = [ + { dimension: 'GeM empanelment', detail: 'Empanelled for relevant IT service categories on the Government e-Marketplace.' }, + { dimension: 'Live government deployments', detail: 'Smart Crematorium Management System for Patna Smart City Limited (PSCL), Bihar Government.' }, + { dimension: 'Multi-district experience', detail: 'Police Management System deployed across 11 districts for the Bihar State Government.' }, + { dimension: 'Records under management', detail: '50,000+ government records managed across live deployments.' }, + { dimension: 'Security posture', detail: 'Role-based access control, full audit trails, OWASP-aligned reviews, encrypted data.' }, + { dimension: 'Uptime track record', detail: '99.9% uptime sustained on critical public-service systems.' }, +]; + +const stats = [ + { value: '11', label: 'Districts deployed' }, + { value: '50,000+', label: 'Government records' }, + { value: '99.9%', label: 'Uptime' }, + { value: 'GeM', label: 'Empanelled vendor' }, +]; + +const faqs = [ + { + question: 'Is WorkRoot a GeM-empanelled vendor?', + answer: + 'Yes. WorkRoot is empanelled for relevant IT service categories on the Government e-Marketplace (GeM), and we have delivered platforms used across 11 districts in Bihar. We can respond to GeM bids and government tenders for web, ERP, and smart-city systems.', + }, + { + question: 'Have you delivered for government clients before?', + answer: + 'Yes. We built the Smart Crematorium Management System (SCMS) for Patna Smart City Limited under the Bihar Government, and a Police Management System deployed across 11 districts for the Bihar State Government, handling personnel, case tracking, and FIR digitisation for 15,000+ officers.', + }, + { + question: 'How do you handle data residency and security for government systems?', + answer: + 'Government data stays in your chosen region on infrastructure you control. We apply role-based access control, encrypt data at rest and in transit, log every action for audit, and run OWASP-aligned security reviews. The same controls run our live Bihar government deployments under strict compliance.', + }, + { + question: 'Can a single platform serve multiple districts?', + answer: + 'Yes — that is exactly what our multi-district architecture is built for. We use a database-per-district model with central aggregation and district-specific feature configuration, so one codebase rolls out across districts without a separate rewrite for each.', + }, + { + question: 'What uptime can you commit to for public services?', + answer: + 'We sustain 99.9% uptime on our mission-critical government deployments through high-availability infrastructure, monitoring, and blue-green deployments. We can align an SLA to the criticality of your service during scoping.', + }, + { + question: 'What technology do you use for government platforms?', + answer: + 'We build on Spring Boot, Astro, and Golang with PostgreSQL and MySQL — the stack behind our SCMS and police deployments. The choice favours long-term maintainability, security, and performance under real public load.', + }, +]; +--- + + + + + +
+ +
+
+ + + + GeM-empanelled · Government IT + +

+ Government IT systems that + roll out across districts and stay up. +

+

+ A GeM-empanelled vendor with secure, audit-ready platforms already live across 11 Bihar districts at 99.9% uptime. + Built on Spring Boot, Astro, Golang and PostgreSQL — with the role-based access, data residency, and compliance public + services demand. +

+ +
+ +
+ {stats.map((stat) => ( +
+

{stat.value}

+

{stat.label}

+
+ ))} +
+
+
+ + +
+
+
+ Why public bodies choose us +

Digitise public services without the rewrite-for-each-district tax

+
+

+ Public-sector technology fails in predictable ways: a system built for one office can’t scale to the next district, + paper processes survive alongside half-finished portals, and security or audit requirements get bolted on too late. + WorkRoot builds government platforms the other way around — multi-district from day one, with audit logging and + role-based access designed into the data layer rather than retrofitted. +

+

+ We are empanelled on the Government e-Marketplace (GeM) and have delivered for real public clients. For + Patna Smart City Limited under the Bihar Government we built and shipped a Smart Crematorium + Management System that now manages 50,000+ records across 10+ facilities. For the Bihar State + Government we delivered a Police Management System deployed across 11 districts, digitising FIRs, + case tracking, and personnel administration for 15,000+ officers. Both run at 99.9% uptime. +

+

+ Our architecture is deliberately conservative where it counts. We favour a database-per-district model with central + aggregation so each district’s data stays isolated while leadership still gets a consolidated view. Offline-resilient + design keeps field-critical modules working through patchy connectivity. Every sensitive action is written to an + immutable audit log, access is governed by role-based permissions, and data is encrypted both at rest and in transit. + Data residency stays under your control — on-premise, in your government cloud, or managed by us within your region. +

+

+ Just as importantly, you own what we build. Full source-code ownership, documentation, and deployment access are part + of delivery, so your department is never hostage to a single vendor. That combination — GeM empanelment, a real + multi-district track record, and clean handover — is why public bodies trust us with services citizens depend on. +

+
+
+
+
+ + +
+
+
+

What we deliver for government

+

Every capability below is running in a live public-sector deployment today.

+
+
+ {capabilities.map((c) => ( +
+ +

{c.title}

+

{c.body}

+
+ ))} +
+
+
+ + +
+
+
+
+

Tender-ready at a glance

+

What we bring to a government engagement.

+
+
+ + + + + + + + + + {readiness.map((row, i) => ( + + + + + ))} + +
WorkRoot government IT readiness and track record
CriterionWorkRoot
{row.dimension} + + + {row.detail} + +
+
+
+
+
+ + +
+
+
+
+ Government case studies +

Live public-sector deployments

+
+
+ +
+

SCMS for PSCL, Bihar Government

+

Patna Smart City Limited · Astro · Golang · PostgreSQL

+

+ A Smart Crematorium Management System digitising slot booking, real-time availability, digital record-keeping, and + automated reporting — cutting booking from hours to minutes across 10+ facilities. +

+
+ {[{ v: '10+', l: 'Facilities' }, { v: '50,000+', l: 'Records' }, { v: '99.9%', l: 'Uptime' }].map((s) => ( +
+

{s.v}

+

{s.l}

+
+ ))} +
+ + Full case study + + +
+ +
+

Police Management System — Bihar

+

Bihar State Government · Spring Boot · Angular · MySQL

+

+ A centralised system across 11 districts handling personnel management, FIR digitisation, case tracking, and duty + roster scheduling — with role-based access and strict security compliance for thousands of concurrent users. +

+
+ {[{ v: '11', l: 'Districts' }, { v: '15,000+', l: 'Officers' }, { v: '100,000+', l: 'Cases' }].map((s) => ( +
+

{s.v}

+

{s.l}

+
+ ))} +
+ + Police system details + + +
+
+
+
+
+ + + + + +
diff --git a/src/pages/services/police-management-system.astro b/src/pages/services/police-management-system.astro new file mode 100644 index 0000000..d14500b --- /dev/null +++ b/src/pages/services/police-management-system.astro @@ -0,0 +1,285 @@ +--- +// Police Management System — keyword-focused service landing page. +// Reuses GuaranteeBand, InlineLeadForm and ServiceFaq, and feeds Service + FAQ +// schema into SEO.astro. +// +// Case-study numbers are taken verbatim from the Police Management System +// entry on /portfolio: 11 districts · 15,000+ officers · 100,000+ cases. +import BaseLayout from '../../layouts/BaseLayout.astro'; +import SEO from '../../components/SEO.astro'; +import GuaranteeBand from '../../components/GuaranteeBand.astro'; +import InlineLeadForm from '../../components/InlineLeadForm.astro'; +import ServiceFaq from '../../components/ServiceFaq.astro'; + +const pageTitle = 'Police Management System Development'; +const pageDescription = + 'Custom Police Management System development — FIR digitisation, case tracking, personnel & duty rosters. WorkRoot’s platform runs across 11 Bihar districts for 15,000+ officers.'; + +const serviceName = 'Police Management System Development'; +const serviceDescription = + 'Custom Police Management System software for state and district law-enforcement bodies — FIR digitisation, case tracking, personnel management, duty-roster scheduling, and real-time reporting with role-based access control. Built on Spring Boot and Angular, deployed across 11 districts in Bihar for 15,000+ officers.'; + +const modules = [ + { title: 'FIR digitisation', body: 'Digital First Information Reports with structured capture, search, and status tracking — replacing paper registers.' }, + { title: 'Case tracking', body: 'End-to-end case lifecycle from registration to disposal, with 100,000+ cases tracked in production.' }, + { title: 'Personnel management', body: 'Officer records, postings, transfers, and service history for 15,000+ personnel.' }, + { title: 'Duty roster scheduling', body: 'Automated duty rosters and shift planning that remove manual scheduling errors.' }, + { title: 'Reporting dashboards', body: 'Real-time dashboards for district and HQ oversight, with scheduled compliance exports.' }, + { title: 'Role-based access control', body: 'Granular permissions by rank, role, and district, with full audit logging of sensitive actions.' }, +]; + +const stats = [ + { value: '11', label: 'Districts deployed' }, + { value: '15,000+', label: 'Officers managed' }, + { value: '100,000+', label: 'Cases tracked' }, + { value: '99.9%', label: 'Uptime' }, +]; + +// Before/after comparison stat-table: manual processes vs the digital system. +const comparison = [ + { dimension: 'FIR filing', before: 'Paper registers, no central search', after: 'Digital FIRs, searchable across districts' }, + { dimension: 'Case status', before: 'Manual file movement, opaque', after: 'Real-time tracking from registration to disposal' }, + { dimension: 'Personnel records', before: 'District-siloed paper files', after: 'Unified service records for 15,000+ officers' }, + { dimension: 'Duty rosters', before: 'Hand-written, error-prone', after: 'Automated scheduling with conflict checks' }, + { dimension: 'Oversight', before: 'Periodic manual compilation', after: 'Live dashboards for HQ and districts' }, + { dimension: 'Data consistency', before: 'Inconsistent across 11 districts', after: 'Single source of truth with audit trail' }, +]; + +const faqs = [ + { + question: 'Have you built a police management system before?', + answer: + 'Yes. WorkRoot developed and deployed a Police Management System for the Bihar State Government across 11 districts. It handles personnel management, FIR digitisation, case tracking, and duty-roster scheduling for 15,000+ officers and 100,000+ cases at 99.9% uptime.', + }, + { + question: 'What modules does a police management system include?', + answer: + 'Core modules are FIR digitisation, case tracking, personnel management, duty-roster scheduling, real-time reporting dashboards, and role-based access control with audit logging. We tailor the module set to your jurisdiction’s workflow during scoping.', + }, + { + question: 'How do you secure sensitive law-enforcement data?', + answer: + 'Through defence-in-depth: role-based access control by rank and district, encryption at rest and in transit, immutable audit logging of every sensitive action, and OWASP-aligned security reviews. The system is built to strict security compliance for thousands of concurrent users.', + }, + { + question: 'Can the system scale across many districts?', + answer: + 'Yes. Our multi-district architecture uses a database-per-district model with central aggregation, so each district’s data stays isolated while HQ gets a consolidated view. The live Bihar deployment already spans 11 districts on a single codebase.', + }, + { + question: 'How long does deployment take?', + answer: + 'Timelines depend on the number of modules and districts. We deliver a usable first module in weeks and roll out district-by-district to manage change and training. We share a detailed plan after the discovery phase.', + }, + { + question: 'What technology stack do you use?', + answer: + 'The police platform is built on Spring Boot for the backend, Angular for the interface, and MySQL for the data layer — chosen for security, maintainability, and performance under heavy concurrent load.', + }, +]; +--- + + + + + +
+ +
+
+ + + + Law-enforcement software + +

+ Police Management System + proven across 11 districts. +

+

+ Digitise FIRs, case tracking, personnel records, and duty rosters in one secure platform — the system we built for the + Bihar State Government already serves 15,000+ officers and tracks 100,000+ cases at 99.9% uptime. +

+ +
+ +
+ {stats.map((stat) => ( +
+

{stat.value}

+

{stat.label}

+
+ ))} +
+
+
+ + +
+
+
+ Built for the field +

From paper registers to a single digital system of record

+
+

+ Before digitisation, police departments across Bihar’s districts relied on paper-based processes for FIR filing, case + tracking, and personnel management. The result was the familiar pattern: delays moving files between offices, + inconsistent records from one district to the next, and no way for headquarters to see the current picture without a + manual compilation. WorkRoot was engaged to replace that with one centralised, secure system. +

+

+ We built a Police Management System on a Spring Boot backend and an Angular + interface, backed by MySQL, and deployed it across 11 districts for the Bihar State + Government. The platform digitises First Information Reports, tracks cases through their full lifecycle, manages + personnel records and postings for 15,000+ officers, and automates duty-roster scheduling. To date it + has handled 100,000+ cases while sustaining 99.9% uptime under thousands of concurrent users. +

+

+ Security and accountability were non-negotiable. Access is governed by role-based permissions tied to rank, role, and + district; every sensitive action is written to an immutable audit log; and data is encrypted both at rest and in + transit. The architecture keeps each district’s data isolated while still rolling up a real-time view for district and + HQ leadership through reporting dashboards — so oversight is continuous rather than periodic. +

+

+ The project spanned four years of delivery and iteration (2018–2022), and the lessons from running at that scale — + offline resilience for field-critical modules, audit logging baked into the data layer, and district-by-district + rollout to manage training and change — now inform every law-enforcement and government engagement we take on. If your + department needs to retire paper and unify records across jurisdictions, we have done exactly that in production. +

+
+
+
+
+ + +
+
+
+

Core modules

+

Each module is running in the live Bihar deployment.

+
+
+ {modules.map((m) => ( +
+ +

{m.title}

+

{m.body}

+
+ ))} +
+
+
+ + +
+
+
+
+

Before and after digitisation

+

The operational change a unified system delivers.

+
+
+ + + + + + + + + + + {comparison.map((row, i) => ( + + + + + + ))} + +
Police operations before and after deploying the WorkRoot Police Management System
AreaBefore (manual)After (WorkRoot)
{row.dimension}{row.before} + + + {row.after} + +
+
+
+
+
+ + +
+
+
+ Case study · Government +

Bihar State Government — Police Management System

+

+ A four-year engagement (2018–2022) delivering a centralised platform across 11 districts, built to handle thousands of + concurrent users with role-based access control and strict security compliance. It remains a reference point for how we + approach multi-district public-sector software. +

+
+ {[{ v: '11', l: 'Districts' }, { v: '15,000+', l: 'Officers' }, { v: '100,000+', l: 'Cases' }].map((s) => ( +
+

{s.v}

+

{s.l}

+
+ ))} +
+ +
+
+
+ + + + + +
diff --git a/src/pages/services/react-native-app-development.astro b/src/pages/services/react-native-app-development.astro new file mode 100644 index 0000000..4ec97ea --- /dev/null +++ b/src/pages/services/react-native-app-development.astro @@ -0,0 +1,280 @@ +--- +// React Native App Development — keyword-focused service landing page. +// Reuses GuaranteeBand, InlineLeadForm and ServiceFaq, and feeds Service + FAQ +// schema into SEO.astro. +// +// Case-study numbers are taken verbatim from the Pophealth entry on +// /portfolio: 10,000+ sessions · 100+ providers · 4.8★ rating. +import BaseLayout from '../../layouts/BaseLayout.astro'; +import SEO from '../../components/SEO.astro'; +import GuaranteeBand from '../../components/GuaranteeBand.astro'; +import InlineLeadForm from '../../components/InlineLeadForm.astro'; +import ServiceFaq from '../../components/ServiceFaq.astro'; + +const pageTitle = 'React Native App Development'; +const pageDescription = + 'Cross-platform React Native & Expo app development — one codebase for iOS and Android, offline-first sync, push notifications, store-ready builds. WorkRoot ships apps rated 4.8★.'; + +const serviceName = 'React Native App Development'; +const serviceDescription = + 'Cross-platform mobile app development with React Native and Expo — a single codebase shipped to both the App Store and Play Store, with offline-first architecture, push notifications, and Spring Boot backend integration. Proven with a health-sessions app handling 10,000+ sessions at a 4.8★ rating.'; + +const capabilities = [ + { title: 'One codebase, both stores', body: 'A single React Native/Expo codebase published to iOS and Android — no separate native teams to fund.' }, + { title: 'Offline-first sync', body: 'Apps that keep working through patchy connectivity and sync cleanly when back online — proven in the field.' }, + { title: 'Push notifications', body: 'Native push on both platforms for re-engagement, reminders, and transactional alerts.' }, + { title: 'Backend integration', body: 'Secure REST integration with Spring Boot and PostgreSQL/MySQL — the same backends behind our web platforms.' }, + { title: 'Store submission', body: 'We handle App Store and Play Store builds, review, and release — not just the code.' }, + { title: 'Native-like performance', body: 'Smooth, responsive UIs that feel native, with platform-aware navigation and gestures.' }, +]; + +const stats = [ + { value: '3+', label: 'Mobile apps shipped' }, + { value: '10,000+', label: 'Sessions handled' }, + { value: '4.8★', label: 'User rating' }, + { value: '2', label: 'Stores, 1 codebase' }, +]; + +// Comparison: cross-platform React Native vs two separate native builds. +const comparison = [ + { dimension: 'Codebases to maintain', native: 'Two (Swift + Kotlin)', rn: 'One (React Native/Expo)' }, + { dimension: 'Time to both stores', native: 'Two parallel builds', rn: 'Single build, ship together' }, + { dimension: 'Team needed', native: 'Separate iOS + Android engineers', rn: 'One cross-platform team' }, + { dimension: 'Feature parity', native: 'Drifts between platforms', rn: 'Identical features by default' }, + { dimension: 'Ongoing cost', native: 'Two maintenance tracks', rn: 'One maintenance track' }, + { dimension: 'Offline support', native: 'Built twice', rn: 'Built once, shared' }, +]; + +const faqs = [ + { + question: 'Why choose React Native over fully native apps?', + answer: + 'React Native lets you ship one codebase to both the App Store and Play Store, so you fund a single cross-platform team instead of separate iOS and Android engineers, get identical features on both platforms, and maintain one codebase. For most products it is faster and cheaper to launch and to keep running, with native-like performance.', + }, + { + question: 'Do you publish to both the App Store and Play Store?', + answer: + 'Yes. We handle the full release path — production builds with Expo/EAS, store metadata, review submission, and the first release — for both Apple’s App Store and Google Play. We can publish under your developer accounts or guide you through setting them up.', + }, + { + question: 'Can the app work offline?', + answer: + 'Yes. We build offline-first architecture with local storage and background sync, so the app stays usable through poor connectivity and reconciles cleanly when the connection returns. Our Pophealth health-sessions app uses exactly this approach for field use.', + }, + { + question: 'How does the app connect to a backend?', + answer: + 'Through secure REST APIs. We typically pair React Native apps with a Spring Boot backend and a PostgreSQL or MySQL database — the same backend stack behind our web and enterprise platforms — so your mobile and web products share one source of truth.', + }, + { + question: 'How long does it take to build a React Native app?', + answer: + 'A focused MVP typically ships in around 6–12 weeks depending on the feature set and integrations. We work in 2-week sprints with a live build available early, so you can test on real devices and steer the roadmap as it develops.', + }, + { + question: 'What does a React Native app cost?', + answer: + 'Mobile builds generally fall in the ₹2,00,000–₹15,00,000 range depending on scope, integrations, and whether a backend is included. Every quote is free, itemised, and fixed-price for well-defined scopes.', + }, +]; +--- + + + + + +
+ +
+
+ + + + Cross-platform mobile + +

+ React Native apps for + iOS and Android — from one codebase. +

+

+ Launch on both stores without the native-team overhead. We build offline-first React Native and Expo apps with push + notifications and Spring Boot backends — and ship them store-ready. Our last health app holds a 4.8★ rating across + 10,000+ sessions. +

+ +
+ +
+ {stats.map((stat) => ( +
+

{stat.value}

+

{stat.label}

+
+ ))} +
+
+
+ + +
+
+
+ Why cross-platform +

One codebase in every customer’s pocket

+
+

+ Building separate native apps for iOS and Android means funding two engineering teams, two release pipelines, and two + sets of bugs — and watching feature parity quietly drift apart over time. React Native collapses that into a single + codebase that ships to both the App Store and Google Play. For the vast majority of products, that means launching + sooner, spending less, and maintaining one track instead of two — without giving up the native-like feel users expect. +

+

+ WorkRoot builds cross-platform apps with React Native and Expo, backed by Spring Boot + APIs and PostgreSQL. We design offline-first from the start, because real users lose signal — in + transit, in basements, in rural areas — and an app that freezes the moment connectivity drops is an app people delete. + Local storage plus background sync keeps the experience smooth and reconciles data the moment the connection returns. +

+

+ Push notifications, secure authentication, deep links, and clean backend integration come standard, and we don’t stop + at the code: we handle the production builds, store metadata, and review submission to get you live on both stores. + Because the backend stack matches our web and enterprise platforms, your mobile app and any web product can share one + source of truth rather than drifting into separate data silos. +

+

+ The proof is in production. Our Pophealth health-sessions app — built with Expo and Spring Boot — went live for a + healthcare client, onboarded 100+ providers, handled 10,000+ sessions with + offline-first sync for areas of poor connectivity, and earned a 4.8★ user rating. If you have a mobile + product to launch, we can take it from idea to both stores. +

+
+
+
+
+ + +
+
+
+

What we ship

+

Everything a production mobile app needs, on both platforms.

+
+
+ {capabilities.map((c) => ( +
+ +

{c.title}

+

{c.body}

+
+ ))} +
+
+
+ + +
+
+
+
+

React Native vs two native builds

+

Why one codebase usually wins.

+
+
+ + + + + + + + + + + {comparison.map((row, i) => ( + + + + + + ))} + +
Comparison of separate native iOS and Android development versus cross-platform React Native
DimensionTwo native appsReact Native (WorkRoot)
{row.dimension}{row.native} + + + {row.rn} + +
+
+
+
+
+ + +
+
+
+ Case study · Mobile +

Pophealth — Health Sessions App

+

+ A healthcare client needed a mobile-first tool to manage patient sessions and health data, with offline capability for + areas of poor connectivity. We built it with Expo (React Native) and a + Spring Boot backend over PostgreSQL, using an + offline-first architecture with seamless sync for session management, appointment booking, and patient tracking. +

+
+ {[{ v: '10,000+', l: 'Sessions managed' }, { v: '100+', l: 'Providers onboarded' }, { v: '4.8★', l: 'User rating' }].map((s) => ( +
+

{s.v}

+

{s.l}

+
+ ))} +
+ + Read the full case study + + +
+
+
+ + + + + +
diff --git a/src/pages/services/university-erp.astro b/src/pages/services/university-erp.astro new file mode 100644 index 0000000..661bcf0 --- /dev/null +++ b/src/pages/services/university-erp.astro @@ -0,0 +1,294 @@ +--- +// University ERP — keyword-focused service landing page. +// Reuses GuaranteeBand, InlineLeadForm and ServiceFaq, and feeds Service + FAQ +// schema into SEO.astro. +// +// Case-study numbers are taken verbatim from the IIT Patna University +// Management System entry on /portfolio: 3,000+ students · 500+ courses · +// 200+ faculty. +import BaseLayout from '../../layouts/BaseLayout.astro'; +import SEO from '../../components/SEO.astro'; +import GuaranteeBand from '../../components/GuaranteeBand.astro'; +import InlineLeadForm from '../../components/InlineLeadForm.astro'; +import ServiceFaq from '../../components/ServiceFaq.astro'; + +const pageTitle = 'University ERP & Management System'; +const pageDescription = + 'University ERP development — admissions, registration, examinations, grading, and faculty management in one platform. WorkRoot built the IIT Patna University Management System.'; + +const serviceName = 'University ERP & Management System'; +const serviceDescription = + 'Custom university ERP and management systems covering the full student lifecycle — admissions, course registration, examination scheduling, grade management, and faculty administration. Built on Next.js and Spring Boot, delivered for the Indian Institute of Technology, Patna.'; + +const modules = [ + { title: 'Admissions', body: 'Online applications, document handling, and seat allocation that replace fragmented manual intake.' }, + { title: 'Course registration', body: 'Self-service registration with prerequisite checks, capacity limits, and timetable clash detection.' }, + { title: 'Examination scheduling', body: 'Exam planning, hall and invigilator allocation, and conflict-free timetabling.' }, + { title: 'Grade management', body: 'Mark entry, moderation, GPA/CGPA computation, and transcript generation.' }, + { title: 'Faculty administration', body: 'Faculty profiles, course assignments, and workload tracking for 200+ faculty in production.' }, + { title: 'Student lifecycle', body: 'A unified record from admission to graduation, with role-based access for staff and students.' }, +]; + +const stats = [ + { value: '3,000+', label: 'Students served' }, + { value: '500+', label: 'Courses managed' }, + { value: '200+', label: 'Faculty onboarded' }, + { value: '1', label: 'Unified platform' }, +]; + +// Fragmented legacy vs unified university ERP comparison. +const comparison = [ + { dimension: 'Admissions', legacy: 'Separate intake tools and spreadsheets', erp: 'One online admissions pipeline' }, + { dimension: 'Registration', legacy: 'Manual forms, clash errors', erp: 'Self-service with prerequisite & clash checks' }, + { dimension: 'Examinations', legacy: 'Standalone scheduling, hall conflicts', erp: 'Conflict-free exam timetabling' }, + { dimension: 'Grading', legacy: 'Disconnected mark sheets', erp: 'Automated GPA/CGPA and transcripts' }, + { dimension: 'Faculty data', legacy: 'Siloed department records', erp: 'Central faculty administration' }, + { dimension: 'Student record', legacy: 'Scattered across systems', erp: 'Single lifecycle record of truth' }, +]; + +const faqs = [ + { + question: 'Have you built a university management system before?', + answer: + 'Yes. WorkRoot built the University Management System for the Indian Institute of Technology, Patna. It manages admissions, course registration, examination scheduling, grade management, faculty profiles, and administrative workflows for 3,000+ students, 500+ courses, and 200+ faculty.', + }, + { + question: 'What modules does a university ERP include?', + answer: + 'A typical build covers admissions, course registration, examination scheduling, grade and transcript management, faculty administration, and the overall student lifecycle — all under role-based access for staff and students. We tailor the exact module set to your institution during scoping.', + }, + { + question: 'Can it replace our existing fragmented systems?', + answer: + 'Yes — that is the usual reason institutions engage us. IIT Patna needed to replace fragmented legacy systems with one unified platform, which is exactly what we delivered. We migrate existing data and consolidate intake, registration, examinations, and records into a single source of truth.', + }, + { + question: 'Will it scale for our whole campus?', + answer: + 'Yes. The IIT Patna platform was designed for scalability and high availability to serve the entire academic community. Our architecture handles concurrent registration and exam periods — the peak-load moments that break smaller systems.', + }, + { + question: 'How long does a university ERP take to deliver?', + answer: + 'We deliver module by module so value lands early — a first module in weeks, with full rollout over a few months depending on scope. Working in 2-week sprints with a live staging environment, your team sees and steers the system as it is built.', + }, + { + question: 'What technology do you use for university ERPs?', + answer: + 'The IIT Patna system is built on Next.js for the interface and Spring Boot for the backend, with MySQL for the data layer — chosen for scalability, maintainability, and high availability across the academic community.', + }, +]; +--- + + + + + +
+ +
+
+ + + + Higher-education software + +

+ University ERP that runs + the whole student lifecycle. +

+

+ Admissions, registration, examinations, grading, and faculty — one platform instead of a dozen disconnected tools. + We built exactly this for the Indian Institute of Technology, Patna, on Next.js and Spring Boot. +

+ +
+ +
+ {stats.map((stat) => ( +
+

{stat.value}

+

{stat.label}

+
+ ))} +
+
+
+ + +
+
+
+ Built for institutions +

One platform for admissions through graduation

+
+

+ Universities accumulate software the way they accumulate buildings — one tool for admissions, another for + registration, a spreadsheet for grades, a separate system for faculty. Each works in isolation, but the seams show at + exactly the wrong moments: registration week, exam season, results day. A university ERP replaces that patchwork with a + single platform that follows each student from application to graduation, and gives staff one place to work. +

+

+ WorkRoot delivered precisely this for the Indian Institute of Technology, Patna. The institution + needed to replace fragmented legacy systems with a unified platform spanning admissions, course registration, + examination scheduling, grade management, faculty profiles, and administrative workflows. We built it on a + Next.js front end with a Spring Boot backend and a MySQL data + layer, engineered for scalability and high availability so it holds up when the whole campus logs in at once. In + production it serves 3,000+ students, 500+ courses, and 200+ faculty. +

+

+ The hard part of academic software is the peak. Registration and examinations concentrate enormous load into a few + days, and the modules have to coordinate — prerequisites gate registration, registration drives exam scheduling, + exams feed grading, grades roll into transcripts. We model those dependencies explicitly so the system stays + conflict-free under pressure: capacity limits and clash detection at registration, hall and invigilator allocation at + exam time, and automated GPA/CGPA computation and transcript generation at results. +

+

+ Role-based access keeps students, faculty, and administrators each seeing only what they should, and the unified + student record becomes a single source of truth that ends the reconciliation scramble between departments. The + platform is yours on delivery — full source code, documentation, and deployment access — so your institution stays in + control of its most important data. If you are ready to retire a fragmented stack, we have built the replacement + before, at an IIT. +

+
+
+
+
+ + +
+
+
+

University ERP modules

+

The full academic lifecycle, in one connected system.

+
+
+ {modules.map((m) => ( +
+ +

{m.title}

+

{m.body}

+
+ ))} +
+
+
+ + +
+
+
+
+

Fragmented tools vs a unified ERP

+

What changes when everything connects.

+
+
+ + + + + + + + + + + {comparison.map((row, i) => ( + + + + + + ))} + +
Comparison of fragmented academic tools versus a unified WorkRoot university ERP
AreaFragmented toolsUnified ERP (WorkRoot)
{row.dimension}{row.legacy} + + + {row.erp} + +
+
+
+
+
+ + +
+
+
+ Case study · Higher education +

University Management System — IIT Patna

+

+ An end-to-end University Management System for the Indian Institute of Technology, Patna — managing student admissions, + course registration, examination scheduling, grade management, faculty profiles, and administrative workflows in one + scalable, high-availability platform. +

+
+ {[{ v: '3,000+', l: 'Students served' }, { v: '500+', l: 'Courses managed' }, { v: '200+', l: 'Faculty onboarded' }].map((s) => ( +
+

{s.v}

+

{s.l}

+
+ ))} +
+
+ “WorkRoot delivered our University Management System for IIT Patna on time and within budget. The Next.js + Spring Boot + architecture is robust and scalable. They are a reliable technology partner for complex enterprise projects.” +
— Dilip Raj, Director, MOC Soft Technologies Pvt Ltd
+
+ +
+
+
+ + + + + +
diff --git a/src/pages/sitemap.astro b/src/pages/sitemap.astro index b1c1d61..ff0614d 100644 --- a/src/pages/sitemap.astro +++ b/src/pages/sitemap.astro @@ -22,10 +22,22 @@ const sitemapSections = [ title: 'Services', icon: 'briefcase', links: [ + { name: 'All Services', url: '/services', description: 'Our full range of IT service offerings' }, { name: 'Web Development', url: '/services#web-development', description: 'Custom web applications and e-commerce' }, { name: 'Mobile Development', url: '/services#mobile-development', description: 'iOS, Android, and cross-platform apps' }, - { name: 'AI & Machine Learning', url: '/services#ai-ml', description: 'Intelligent solutions and automation' }, - { name: 'Cloud Services', url: '/services#cloud', description: 'Cloud migration and infrastructure' }, + { name: 'UI/UX Design', url: '/services#ui-ux-design', description: 'Accessible, conversion-focused interfaces' }, + { name: 'IT Consulting & DevOps', url: '/services#it-consulting', description: 'Architecture, cloud, and CI/CD' }, + ], + }, + { + title: 'Solutions', + icon: 'briefcase', + links: [ + { name: 'Custom ERP Development', url: '/services/custom-erp-development', description: 'Bespoke enterprise systems on Spring Boot & Angular' }, + { name: 'University ERP', url: '/services/university-erp', description: 'Admissions, exams, grading — built for IIT Patna' }, + { name: 'Government IT & GeM Vendor', url: '/services/government-it-solutions-gem-vendor', description: 'GeM-empanelled, live across 11 districts' }, + { name: 'Police Management System', url: '/services/police-management-system', description: 'FIR, case tracking & personnel for 15,000+ officers' }, + { name: 'React Native App Development', url: '/services/react-native-app-development', description: 'One codebase for iOS and Android' }, ], }, { diff --git a/src/pages/sitemap.xml.ts b/src/pages/sitemap.xml.ts index fa34077..a390d62 100644 --- a/src/pages/sitemap.xml.ts +++ b/src/pages/sitemap.xml.ts @@ -25,6 +25,12 @@ export const GET: APIRoute = async () => { const staticPages: SitemapEntry[] = [ { url: '/', changefreq: 'weekly', priority: 1.0 }, { url: '/services/', changefreq: 'monthly', priority: 0.9 }, + // Keyword-focused service landing pages + { url: '/services/custom-erp-development/', changefreq: 'monthly', priority: 0.8 }, + { url: '/services/government-it-solutions-gem-vendor/', changefreq: 'monthly', priority: 0.8 }, + { url: '/services/police-management-system/', changefreq: 'monthly', priority: 0.8 }, + { url: '/services/react-native-app-development/', changefreq: 'monthly', priority: 0.8 }, + { url: '/services/university-erp/', changefreq: 'monthly', priority: 0.8 }, { url: '/portfolio/', changefreq: 'weekly', priority: 0.8 }, { url: '/about/', changefreq: 'monthly', priority: 0.8 }, { url: '/blog/', changefreq: 'weekly', priority: 0.8 },