CS-01Case study visuals in preparation
Healthcare case study
Reserved for a published healthcare engagement — operational software, patient-facing tools or clinical workflows.
We design & engineer software that has to work.
- 01Product Design
- 02Web Engineering
- 03SaaS Development
- 04Enterprise Applications
- 05AI & Automation
- 06Accessibility
Design-led engineering for organizations that take digital seriously.
One team across strategy, interface design and software engineering.
- UI/UX
- Engineering
- Accessibility
- SaaS
- AI
- Healthcare
- Enterprise
- Design Systems
01Philosophy
Good software works.Exceptional software earns trust.
We combine product strategy, interface design and engineering to create digital products that are useful, accessible and built to scale. Not as separate hand-offs — as one practice, from the first workshop to the production release.
- Product strategyWhat to build, for whom, and why it matters.
- Interface designClear, inclusive experiences for complex work.
- EngineeringTyped, tested software built to be maintained.
Six disciplines. One accountable team.
Every engagement draws on the same core capabilities, combined around the problem you need solved.
Product Design
Research-led interface design for products with real complexity.
- User research
- Information architecture
- Prototyping
- Interface design
Web Engineering
Fast, accessible, search-ready platforms on a modern stack.
- Next.js & React
- Performance budgets
- Technical SEO
- Headless CMS
SaaS Development
Multi-tenant products designed to be sold, used and scaled.
- Product architecture
- Auth & roles
- Billing
- Admin tooling
Enterprise Applications
Internal platforms that replace spreadsheets and legacy systems.
- Workflow modeling
- Integrations
- Data migration
- Audit & permissions
AI & Automation
AI features with a clear job, measurable quality and human oversight.
- Assistants
- Document processing
- Retrieval
- Workflow automation
Accessibility
Inclusive products designed and tested against WCAG 2.2 AA.
- Audits
- Remediation
- Accessible components
- Assistive tech testing
Products we are building.
We don't only build for clients. We design, engineer and own software products — which is why we think like product owners on every engagement.
Status: In developmentHealthcare operations
Healthcare Management Platform
Modern healthcare operations, built for the way care works today.
A unified operations platform for clinics and hospitals — appointments, patient records, clinician schedules, administration, communication and reporting in one accessible, secure workspace.
Illustrative interface preview of the Appointments module, using sample data.
How we help teams build.
Eight services, delivered by one team. Start with one, or combine them into an end-to-end engagement.
Product strategy turns an idea or an existing product into a clear, prioritized plan: the users, the problems worth solving, the scope of a first release and the technical approach behind it.
- Deliverables
- Discovery workshops
- User and stakeholder research
- Product requirements
- Prioritized roadmap
- Technical approach
- Technology
- Outcome
- A scoped, de-risked plan that design and engineering can execute with confidence.
User experience and interface design for web applications and platforms: information architecture, user flows, interactive prototypes and production-ready interface design.
- Deliverables
- Information architecture
- User flows
- Wireframes
- Interactive prototypes
- High-fidelity UI
- Usability testing
- Technology
- Outcome
- An interface that users understand quickly and engineers can build precisely.
Engineering for marketing sites, content platforms and web applications — built with modern frameworks, performance budgets and accessibility from the start.
- Deliverables
- Frontend architecture
- CMS integration
- Technical SEO
- Performance optimization
- Accessibility implementation
- Analytics setup
- Technology
- Outcome
- A site that loads quickly, ranks well, converts and is straightforward to maintain.
End-to-end design and engineering of software-as-a-service products: authentication, multi-tenancy, billing, dashboards and the domain logic that makes the product valuable.
- Deliverables
- Product architecture
- MVP build
- Authentication and roles
- Billing integration
- Admin tooling
- Automated testing
- Technology
- Outcome
- A product customers can use and a codebase your team can keep building on.
Bespoke applications that replace spreadsheets, manual processes and legacy systems — portals, back-office tools, dashboards and integrations.
- Deliverables
- Workflow analysis
- System architecture
- Web application
- Integrations and APIs
- Data migration
- Documentation
- Technology
- Outcome
- Software that fits the work — reducing manual effort and operational risk.
A shared language between design and engineering: design tokens, accessible component libraries, usage guidelines and the governance to keep them healthy.
- Deliverables
- Interface audit
- Design tokens
- Figma component library
- Coded component library
- Documentation
- Contribution model
- Technology
- Outcome
- Faster delivery, fewer inconsistencies and accessibility built into every component.
Accessibility audits, remediation and training for websites and applications, measured against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
- Deliverables
- Manual and automated audit
- Prioritized issue log
- Remediation
- Assistive technology testing
- Team guidance
- Accessibility statement support
- Technology
- Outcome
- A measurably more accessible product and a team that knows how to keep it that way.
Design and engineering of AI-powered features — assistants, document processing, search and automation — with attention to reliability, privacy and human oversight.
- Deliverables
- Use-case assessment
- Prototype
- Retrieval and data pipelines
- Evaluation framework
- Production integration
- Monitoring
- Technology
- Outcome
- AI that solves a defined problem, with measurable quality and clear limits.
A process built for clarity, not ceremony.
Six stages, each with concrete outputs. You always know where the project stands, what comes next, and why.
- 01
Discover
We learn the business, the users and the constraints. Assumptions get written down so they can be tested.
- Stakeholder interviews
- User research
- Technical audit
- 02
Define
We turn what we learned into a scope: the problems worth solving, success measures and a realistic plan.
- Product requirements
- Roadmap
- Architecture outline
- 03
Design
Flows, prototypes and interfaces — tested with users and reviewed by engineers before they are final.
- User flows
- Prototypes
- Design system
- 04
Build
Iterative engineering in short cycles, with working software to review every sprint — not a big reveal at the end.
- Sprint demos
- Typed, tested code
- CI/CD pipeline
- 05
Validate
Accessibility, performance, security and usability checks against the standards agreed in Define.
- Accessibility testing
- Performance audit
- QA sign-off
- 06
Launch
A planned release, monitored in production, followed by measurement and the next round of improvements.
- Release plan
- Monitoring
- Handover & support
Work across healthcare, enterprise and SaaS.
Detailed case studies are being prepared with client approval. We publish real outcomes only — never estimates dressed up as results.
- CS-02Case study visuals in preparation
Enterprise case study
Reserved for a published enterprise engagement — internal platforms, portals or legacy modernization.
- CS-03Case study visuals in preparation
SaaS case study
Reserved for a published SaaS engagement — a product built from first release to scale.
- CS-04Case study visuals in preparation
Accessibility case study
Reserved for a published accessibility engagement — audit, remediation and inclusive redesign.
07Accessibility
Accessibility is not an add-on.
We design and engineer interfaces with accessibility considered from the first sketch — in the design system, the components and the code — rather than audited in at the end.
We don't make blanket compliance claims. Conformance is assessed per product, against a stated standard, with documented testing.
WCAG 2.2 AA as the baseline
The Web Content Accessibility Guidelines are our design and acceptance criteria, not an afterthought.
Semantic HTML
Real buttons, links, headings, landmarks and form controls — so assistive technology understands the page.
Keyboard navigation
Every interaction works with Tab, Shift+Tab, Enter, Space, Escape and arrow keys where expected.
Screen reader support
Tested with screen readers, with meaningful names, states and announcements.
Color contrast
Color tokens validated for contrast in every theme — and color is never the only signal.
Visible focus states
A clear, consistent focus indicator on every interactive element.
ARIA where appropriate
ARIA fills genuine gaps in HTML. It never replaces native semantics.
Reduced motion
Animation respects the reduced-motion preference and never carries essential meaning.
Built differently.
The difference is not a methodology slide. It is how the work is organized, who is in the room, and what we refuse to cut.
Design and engineering, one team
Designers and engineers work in the same room from day one. Nothing is thrown over a wall.
Product thinking
We build products ourselves, so we think in outcomes, trade-offs and roadmaps — not just tickets.
Accessibility first
Inclusive design is a starting constraint, not a post-launch audit.
Modern architecture
Typed, tested, documented code on a stack chosen for the problem, not for the trend.
Transparent process
Working software every sprint, a shared backlog and honest estimates — including the uncomfortable ones.
Long-term partnership
We design for the second year of a product, not only the launch day.
An engineering, design and product company.
Notes on building software properly.
Practical writing on product, design, engineering and accessibility — from the work, not the trend cycle.
Why accessibility should begin at the design system
Most accessibility defects are not page problems. They are component problems, repeated hundreds of times. Fix them once, at the source.
Design systems that survive real products
A design system is not a Figma file. It is an agreement between design and engineering — and agreements need maintenance.
Building SaaS products for complex workflows
Complex domains punish generic software. The hard part is not the features — it is modeling the work correctly.
Questions, answered plainly.
AMPDUO Studio (also known as AMPDUO) is a product design and software engineering studio. It designs and builds SaaS products, custom software, accessible websites and design systems for clients, and develops proprietary software of its own, starting with a healthcare management platform.
AMPDUO Studio designs and engineers digital products: SaaS platforms, custom software, websites and design systems. We also build proprietary software, starting with a healthcare management platform.
Startup founders, SaaS companies, enterprise teams and healthcare organizations — typically teams building software that has to be reliable, accessible and maintainable over years.
AMPDUO Studio is based in Vadodara, Gujarat, India. We work with clients in Vadodara and across Gujarat in person, and remotely with teams across India, the United States, the United Kingdom and Europe.
Our core stack is TypeScript, React, Next.js and Node.js with PostgreSQL, deployed on AWS or Vercel. We also work with Angular, Supabase, Figma for design and Playwright for automated testing.
Yes. We design and build to WCAG 2.2 level AA as a target and test with keyboards, screen readers and automated tools. Conformance is verified per project rather than assumed.
With a short conversation about what you are building, followed by a discovery phase that defines scope, priorities and a realistic plan before design and development begin.
Have something worth building?
Tell us what you're working on. We'll help turn the idea into a product people can trust.