Design & development studio
Every question put to us over seven years, sorted and answered without the sales gloss. Search it, or start from a category.
Niasa is a digital product design and development studio: websites, user interfaces, custom software and mobile apps. Work starts with a consultation and information architecture, moves into design in Figma, is built with custom code, and is handed over with training and a support period.
Because a whole team runs your project, not one person. A designer, a front-end developer, a back-end developer and a project manager are on it from day one — which means one person's holiday or workload never stops your project, and quality isn't tied to a single person's taste.
A small, stable team: a project manager as your single point of contact, a UI designer, a developer, and — where it's needed — an SEO or content specialist. The team doesn't change mid-project, and the people in your meetings are the ones writing the code and the design.
Yes — a large share of our projects have run exactly that way. Meetings are online, the contract is signed electronically, and the whole project — from Figma to the preview link — is available to you online. Our Tehran office is always open for a meeting in person, too.
E-commerce, finance and currency exchange, industry and manufacturing, travel, health, and professional services. More important than the list, though, is that our process starts by understanding your business: the first meeting is for learning, not for selling.
Yes. A single landing page, a redesign of a few key pages, or a performance rescue on an existing site are all real projects. If something falls outside what we do well, we say so plainly and, where we can, point you to a better-suited team.
A price rests on three things: scope (how many pages and features), depth of design (bespoke, or built on an existing system) and technical complexity (integrations, custom dashboards, data volume). After a free consultation you get a proposal with a fixed price and an exact schedule.
So you have a picture before you even call, every service page carries packages with a starting price and an interactive estimator: pick the options your project needs and the range appears there and then. The final figure is settled after the consultation, in the proposal.
In stages, tied to real deliverables: a deposit on signing, one stage on design approval, one on build completion, and the balance at final handover. Longer projects can be split monthly instead.
Yes, because they are annual third-party services and are best bought in your own name, so you keep ownership of them. We help you choose and set them up, and if you'd like, we take over their technical management under a maintenance contract.
Contracts and invoices are issued by Andisheh Mandegar Rayan, and formal VAT invoices are available for companies. Corporate and staged payments are no problem.
A new request is never refused — but it is never absorbed silently either. Its effect on time and cost is estimated and put in writing, and it enters the scope once you approve it. Small changes that don't move the schedule are made at no cost.
With a call or a short form. In the free consultation — in person or online, around 45 minutes — we talk about your business, your audience and what the project is for. The output is a proposal with scope, price and schedule, with no obligation to continue.
Between 2 and 14 weeks depending on scope. The schedule is put in writing before work starts, and you get a progress report every week.
Six clear ones: consultation and discovery, information architecture and wireframes, UI design, build, testing and optimisation, then launch and training. Each stage ends with something you can look at, not a status report.
Less than you'd think, but at the right moments. Three to five short meetings across the project and feedback within 48 hours is enough. Most of your time goes where the decisions are made: approving the information architecture and approving the design.
Yes. From week one you have a live preview link that updates with every change — so you never have to wait for a reveal at the end.
Delays on our side are made good, and the contract says so. The most common cause of delay, though, is late content and feedback from the client — which is why the schedule names your deadlines too, so neither side is caught out.
No. Every project is designed and coded from scratch, which is why your site looks like nobody else's and its speed isn't hostage to a stack of plugins.
Yes. You get a content management panel and training on it — a live session plus a recording — as part of handover. Editing text, images, products or articles needs no technical knowledge.
Yes, and it's one of the things we do best. A multilingual site is more than translated text: layout direction, numerals, calendars, a font per language and separate URLs for search engines all have to be right. The site you're reading is bilingual and fully right-to-left.
Yes. A personal site is for anyone who is the brand: doctors, lawyers, lecturers, consultants, photographers, artists and freelancers. What you get is a fixed address in your own name that carries your CV, portfolio, writing and contact details in full — and ranks in Google under your name.
Yes. A medical site isn't a corporate site with a photograph of a doctor on it; the patient's route from search to booked appointment has to be frictionless. Online booking is built with a calendar, capacity per practitioner, SMS reminders and optional deposits — and connects to the practice software you already run.
Yes, and there's a set routine for it: the existing URLs are mapped, every one gets a 301 redirect to its new equivalent, heading structure and schema carry across, and rankings are watched closely in the first weeks after launch.
Yes: cart, payment gateways, stock and product variants, shipping methods, discounts and coupons, invoicing, and a sales dashboard. There's no limit on product count, and search and filters are tuned for the catalogue you actually have.
Yes. Many of our clients have their own engineering team and want the design alone. In that case the deliverable is a tidy, extensible Figma file with an implementation guide, so your team can build it without a round of back-and-forth.
A layered Figma file with named components and styles, desktop and mobile versions of every screen, each component's states (empty, loading, error), and a handoff page with colour, type and spacing tokens.
Two formal rounds per stage are written into the contract, but in practice we stay with it until it's right. In our experience, when discovery is done properly, revisions rarely reach two rounds at all.
Yes, on projects whose scale justifies it: user interviews, competitor review, user-journey analysis and usability testing on a clickable prototype. On smaller projects a compressed version of the same work happens inside the discovery session.
A design system means that instead of designing page by page, we build the product's shared language: colours, typography, spacing and the components that repeat. If your product will grow for years, or several people will work on it at once, it saves months later.
Next.js and React with TypeScript on the front end; Node.js and Laravel on the back end; PostgreSQL and MySQL for data; React Native and Flutter for mobile. The stack is chosen for the project rather than out of habit — and we'll explain the reasoning.
Yes, over APIs — and we've worked with the systems common in Iran: accounting software, SMS services, payment gateways and courier companies. If your system has no API, we look at the alternatives with you.
Before promising anything, we audit the code and tell you honestly whether continuing or rewriting is the better buy. Sometimes rescuing old code costs more than replacing it, and saying so is part of the job.
The architecture is written for growth from the start: layered caching, tuned queries, responsive images and CDN distribution. For projects where it matters, we load-test before launch so you know your ceiling — rather than discovering it on campaign day.
By following OWASP practices in the code, validating input, encrypting sensitive data, requiring two-factor authentication on the admin panel, updating dependencies regularly and backing up automatically. SSL and server hardening are part of setup.
Yes. If a mobile app, an admin panel or another service has to talk to your system, we design a documented, versioned API and hand the documentation over with the project.
For most businesses cross-platform (React Native or Flutter) is the right call: one codebase, two platforms, less time and cost. Native earns its premium when heavy graphics performance or deep hardware access is involved.
Yes — build packaging, store icons and screenshots, listing copy, and shepherding each store's review. Developer accounts are created in your name so you own the app from day one.
Mostly it comes down to the number of screens, how complex the logic is, and whether the back end is built from scratch or connects to something you already run. To start, we usually suggest a minimal version carrying the product's core value, with the rest added after real user feedback.
Sometimes it's exactly right: installable on the home screen, works offline, no store gatekeeping. But if you need strong push notifications, deep hardware access or a presence in the app stores, an app is the answer. We separate the two for you in the consultation.
Technical SEO is part of every project and is never sold separately: correct semantic structure, titles and descriptions, schema, sitemap, clean URLs, speed and the mobile version. What is separate is content SEO and link building — ongoing monthly work by nature.
Honestly: nobody can guarantee a given position by a given date, and anyone who promises one deserves suspicion. What we do guarantee is a flawless technical foundation; visible results usually arrive between months three and six, alongside regular publishing.
Every project targets green Core Web Vitals: LCP under 2.5s (usually under 1.2s on custom builds), CLS near zero and a short INP. Speed comes from optimised images, lean code, caching and lazy loading — not from a plugin bolted on at the end.
Yes, as an add-on: copywriting for the main pages, content structure for service pages, and a publishing calendar for the blog. If you write it yourself, we give you the framework and a word count per section so the words and the design fit each other.
Measurement is installed and configured from launch day: Google Analytics, Search Console, and events for the things that matter — a form submitted, a phone number tapped. During the support period you get a readable monthly report, not a raw export.
Every project ships with a free support period, its length set in the contract (typically 3 to 6 months depending on the project). After that, a monthly or annual maintenance contract is optional and never a condition of your site continuing to work.
Fixing technical faults, security updates, backups, uptime monitoring, and help using the panel. Small content changes usually happen inside it too; building a new feature, though, is a small project of its own.
During business hours, messages are usually answered in under 15 minutes. For critical failures — the site is down, or payments aren't going through — you have a 24/7 emergency channel.
Yes: automated, scheduled backups of files and database, kept somewhere other than the main server. More important than taking a backup is testing the restore, so restores are exercised periodically — the day you need one is the wrong day to find out.
Yes, under a maintenance contract: server setup, SSL, updates, resource monitoring and responding to alerts are ours, and you simply pay the provider's bill. If you'd rather, we hand the whole thing to your own technical team.
Once the proposal is approved, a formal contract with Andisheh Mandegar Rayan sets out scope, schedule, amounts and payment stages, both parties' obligations, and termination terms. It can be signed in person or electronically.
You do. The repository, the Figma file, the technical documentation and every credential are handed over in the client's name. Nothing stays behind with us — if you want to continue with another team tomorrow, there's no lock in your way.
Yes, before any technical discussion and whenever you ask. Business information, user data and product ideas are treated as confidential, and access is limited to the people on that project.
Termination terms are in the contract from the start: settlement for the work done and delivered up to that point, and that work handed to you. A project doesn't end with one email — but nothing is held hostage either.
Only with your permission. If a project is confidential, or you'd rather its name wasn't published, it stays off the list. On many projects, publishing with name and logo is agreed in writing instead.
Yes. We guide and follow up the Enamad trust seal and Samandehi licence, and the technical prerequisites — terms page, contact details, a licensed gateway — are built into the site from the start.
Our team answers around the clock — one message is enough to get your project moving.
Tell us about your plan; we're with you until it ships. We answer 24 hours a day, 7 days a week.
