Rauni Medical Centre
Appointments and care information for a family medical centre
Get booked · Design and apps
UI/UX design design that survives contact with the code
Screens designed around what customers came to do, checked for clarity and accessibility before they are built.
At a glance
- Research → journey maps → IA → prototypes
- Design systems in Figma
- WCAG 2.1 AA designed in, not retrofitted
- Handoff to the same team that writes the code
What a typical engagement includes
- Discovery: stakeholder interviews, analytics review, and an honest read of the current experience
- User research and journey mapping, with the drop-off points named
- Information architecture: sitemap, navigation model, and what each page owes the visitor
- Wireframes at mobile width first, then desktop
- An interactive prototype real people can click through
- Moderated usability testing, with findings folded back in before code starts
- Visual design and a Figma component library, with variants and every state drawn (including empty, loading, and error)
- Accessibility annotations: focus order, labels, alternative text, contrast pairs
- Design tokens, dev-ready specs, and design review during the build itself
UI/UX design, in detail
User research, journey maps, prototypes and design systems built to WCAG 2.1 AA by the same team that writes the code. No intent lost at handoff.
Design usually goes wrong twice on the same project. First when research is skipped and the team designs for itself: navigation that makes perfect sense to the people who run the business and to nobody else. Then again at handoff, when a beautiful Figma file crosses to a development team that was never in the room, and a good share of the intent quietly evaporates in translation. Spacing drifts. States go missing. The empty screen nobody drew gets improvised.
We remove the second problem structurally: the company that designs it writes the code. Client leadership in Brampton, engineering in Patiala, one file, one team, no translation layer.
What UI/UX design means in our hands
Research sized for a real business. Five to eight conversations with the people who actually use the thing, a journey map of how they get from problem to purchase, and the two or three moments where they currently give up. That's a week of work, and it changes more decisions than a sixty-slide persona deck. If you already have support tickets, session recordings, or site-search logs, we mine those first, because they're free and honest.
Accessibility is a design decision, not a dev ticket. Contrast, focus order, touch target size, error messaging, and keyboard paths are settled in Figma against WCAG 2.1 AA, before there's a component to retrofit. Bolted on after a build, accessibility is expensive. Designed in, it costs almost nothing and quietly improves the interface for everyone.
A design system, not a pile of screens. You get a component library with tokens for colour, type, spacing, and radius that map to the code the same way, so the twentieth screen your team needs next year can be assembled without a designer in the room, and without the brand drifting.
The approach and the toolkit
- Figma for everything: library, variants, prototypes, annotations, and a file you own outright
- Mobile-first frames, because most traffic arrives on a phone and squashing a desktop layout is exactly why so many sites feel cramped
- Tokens that map to Tailwind, so the design system and the codebase describe the same values instead of agreeing by accident
- Performance budgeted in design: type, imagery, and motion vetted for load time before they reach a build, then measured on a real phone before launch
- Tested on real devices, with keyboard and screen reader, not only on a 27-inch monitor
What this looks like in practice
A redesign where the numbers say something is wrong. Traffic arrives and doesn't convert, or support answers the same question forty times a month. Research and journey mapping locate the actual break, the architecture gets rebuilt around it, and a prototype is tested before anyone writes code. This usually pairs with a web design or webapp build.
A design system for a product that outgrew its screens. An audit of what exists today, a token set and component library with documented usage rules, and a handoff that lets your team ship new features consistently. Common alongside mobile app work, where two platforms multiply the drift.
Pricing
UI/UX work is scoped per project. A focused research and prototype sprint and a full design system for a multi-platform product are different engagements, so we quote after a short call rather than from a rate card. Design bundled with a build is scoped as one project, not two invoices. Contact us for a quote.
Planning the work
Resolve how the product works before polishing how it looks.
What to cover in the scope
- Map the main user tasks and decisions.
- Design navigation, forms and empty, loading and error states.
- Review an interactive flow and document the decisions needed for implementation.
What helps us plan
Bring user feedback, existing screens and the tasks people struggle to complete. Agree the target devices and which journeys are in scope before counting screens.
How to judge the result
Judge task completion, clarity and accessibility. Attractive individual screens still need to work together when a user makes a mistake or has incomplete information.
From your first message to every month after.
Tell us what to fix
A few lines on the form, or ask the assistant. A person replies within 4 business hours.
A call, then your plan
What to fix first and why, what we'd build and run, the price and the go-live date, in writing within two business days.
We build and launch
A website takes 2 to 6 weeks, a web app 8 to 16. Tested on real phones before launch.
We run it, every month
Hosting, updates and the systems kept working. Monthly plans cancel any time.
Straight answers before you sign
You own everything.
Your code, your domain, your accounts and your data.
One contract, your currency.
You sign with Redenn Informatics Pvt. Ltd. (India) and are invoiced in your own currency. North American work is led from our Brampton, Ontario office (Redenn Informatics Inc.).
Tested on real phones.
Built mobile-first, load time measured before launch, designed to WCAG 2.1 AA.
Prices published.
Websites from $1,200, web apps from $15,000, monthly systems $149 to $249/mo plus setup from $500, and care from $49/mo.
Quoted and invoiced in your own currency by Redenn Informatics Pvt. Ltd. (India); pay by card through Razorpay or by bank transfer.
Questions about UI/UX design
Design is quoted per project rather than from a rate card, because scope varies enormously: mobile-first wireframes for a single flow is a much smaller job than full discovery, user research, journey mapping, a complete component library and moderated usability testing. The main cost drivers are how many screens and states need designing, whether research and testing are included, and whether a design system is being built from scratch. If we are also building the product, design and development are quoted together — one project and one invoice, not two. Either way the number is fixed in writing before work starts, with no surprise add-ons.
Yes. You get a Figma file you own outright, an interactive prototype, design tokens and dev-ready specifications your developer can build from directly — including accessibility annotations covering focus order, labels, alternative text and contrast pairs, which most handoffs leave out. The component library arrives with variants and every awkward state drawn — empty, loading and error — the screens developers are otherwise left to improvise. Because we write code ourselves, the specifications read the way developers actually need them to, and design review during your build is available so what ships matches what was approved.
You can skip it, and for a small marketing page that is sometimes the right call — the scoping conversation is where we tell you honestly which phases earn their cost. But research exists because founders and their users disagree more often than anyone expects, and discovering that in a moderated usability test on a prototype costs far less than discovering it after launch in the built product. Journey mapping and information architecture do the same job even earlier, catching structural problems while they are still drawings. The engagement is modular, so you buy the phases your actual risk justifies.
Tell us where customers slip away. We'll write the plan.
A person replies within 4 business hours. Your written growth plan follows within two business days.
Or call +1 437 524 3001 or toll-free +1 888 905 4003, or email hello@redenn.com.