Question 1

Is it "House of Mohny" or "House of Mohini"?

Accepted Answer

House of Mohny — spelled M-o-h-n-y. The name comes from our founder, Mohnish M. Search engines sometimes autocorrect it to "Mohini" (a common Indian name), but we are a Bengaluru-based AI consulting and web development studio, unrelated to any similarly named business.

Question 2

Who is behind House of Mohny?

Accepted Answer

The studio was founded in 2026 by Mohnish M, who leads strategy, architecture, and delivery on every engagement personally. We are a boutique, senior-led team by design — no junior handoffs, no account managers between you and the work.

Question 3

Why don't you publish exact prices?

Accepted Answer

Because the right investment depends on your specific situation. A website for a pre-launch startup and a website for an enterprise product require completely different levels of research, strategy, and engineering. We give precise proposals once we understand your problem — usually within 3 business days of the strategy call.

Question 4

What are your typical investment ranges?

Accepted Answer

We deliberately do not publish ranges — every engagement is scoped and quoted individually, because a fixed menu either overcharges simple projects or under-serves complex ones. After a free strategy call you receive one written quote with the full price, milestones, and timeline. Our Pricing page explains exactly what drives cost.

Question 5

Do you work on retainer or project basis?

Accepted Answer

Both. For defined scope work, we use fixed-price project contracts — you know exactly what you are paying before we start. For ongoing work (continuous improvement, marketing management, AI iteration), we use monthly retainers with a defined scope of work.

Question 6

What is your payment structure?

Accepted Answer

Typically a deposit on kick-off, milestone payments tied to visible progress, and the balance on final sign-off. Longer engagements (3+ months) bill monthly. Payments are in INR via Razorpay; international clients can be invoiced by bank transfer.

Question 7

Do you work with equity?

Accepted Answer

Occasionally, for the right early-stage opportunity where we genuinely believe in the product and team. This is the exception, not the rule. Be upfront about it in the strategy call — we will tell you honestly whether it is a conversation worth having.

Question 8

How long does a typical project take?

Accepted Answer

Starter projects: 3–6 weeks. Growth projects: 8–16 weeks. Enterprise programmes: 3–12 months. Every engagement starts with a strategy phase that produces a specific timeline with milestones before we commit to a start date.

Question 9

What does the process look like?

Accepted Answer

Discovery → Strategy → Design → Development → Launch → Growth. Discovery and Strategy are typically 2–3 weeks combined. We do not skip these phases — projects that skip discovery almost always require expensive rework mid-build.

Question 10

How involved do I need to be?

Accepted Answer

We ask for about 2–3 hours per week during active development: one 30-minute check-in, one review session on staging, and async feedback via Notion or Linear. We do not need daily availability, but we do need decision-makers accessible — delays in decisions are the most common cause of project delays.

Question 11

Can you work faster if I need it?

Accepted Answer

Yes, with constraints. Rushing removes the Discovery phase, which increases rework risk. Rushing Development increases defect risk. If speed is a genuine business constraint, we will tell you what corners are safe to cut and which are not.

Question 12

What happens if the scope changes mid-project?

Accepted Answer

We handle scope changes through a formal change request process. If the change is minor, we absorb it. If it affects the budget or timeline materially, we send a change order before proceeding. No surprises.

Question 13

Who owns the code when the project is done?

Accepted Answer

You do. Entirely. All source code, design files, and documentation are transferred to you on final payment. We retain no rights to the deliverables. We may ask to include it in our portfolio — this is always optional and subject to your approval.

Question 14

Can I hire someone else to maintain the code?

Accepted Answer

Yes. We build with standard, well-documented technologies precisely so that any competent developer can pick it up. We do not use proprietary tools or lock you into us for maintenance.

Question 15

Do you retain rights to design assets?

Accepted Answer

No. Design files (Figma, image assets, icons) transfer with the code on final payment. The only exception would be if we used licensed third-party assets — we will always flag those with their specific licensing terms.

Question 16

What about open source components you use?

Accepted Answer

We use open source libraries that have permissive licences (MIT, Apache 2.0, BSD). We maintain a full list of third-party dependencies with their licence types as part of the technical documentation handoff.

Question 17

Where do you recommend hosting?

Accepted Answer

Vercel for Next.js applications (globally distributed edge network, automatic CI/CD, first-class Next.js support). AWS or GCP for complex backend services. Cloudflare for DNS and CDN. We do not require a specific provider — we will work with what you already have if it is appropriate.

Question 18

Can you host on GoDaddy/cPanel?

Accepted Answer

Yes, with Phusion Passenger for Node.js applications. It is not our preferred environment (no edge delivery, manual scaling), but it works for lower-traffic applications and is straightforward to set up.

Question 19

What are the ongoing hosting costs?

Accepted Answer

For most projects: Vercel Hobby plan is free for low traffic; Pro plan is $20/month. Domain registration: roughly ₹800–1,500/year. If your project requires a database, add $5–25/month for Supabase or PlanetScale. We itemise all expected infrastructure costs in our proposals.

Question 20

Do you set up monitoring?

Accepted Answer

Yes. Every project includes a monitoring setup: uptime monitoring (UptimeRobot or Better Uptime), error tracking (Sentry), and Core Web Vitals tracking via Vercel Analytics or Google Search Console. You get alerts before your users notice problems.

Question 21

Do you offer ongoing maintenance?

Accepted Answer

Yes. We offer monthly maintenance retainers that include: dependency updates, security patches, performance monitoring, and a bank of hours for small improvements. Ask about current retainer pricing during the strategy call.

Question 22

What happens if there is a bug after launch?

Accepted Answer

Every project includes a 30-day post-launch support window (60 days for Growth projects, 90 days for Enterprise). Bugs discovered during this period are fixed at no additional cost. After the support window, bug fixes are handled via retainer or a separate engagement.

Question 23

How quickly do you respond to urgent issues?

Accepted Answer

On retainer: critical issues (site down) within 2 hours, high-priority issues (payment failure, data loss) within 4 hours. Non-urgent issues within 1 business day. Outside of retainer, we do our best but cannot guarantee response times.

Question 24

Can you train my team to maintain the site?

Accepted Answer

Yes. Knowledge transfer is included in every project. We provide documentation, a recorded walkthrough of the codebase, and a Q&A session. If you want ongoing training beyond this, we can include it in a retainer or charge a day rate.

Question 25

Is SEO included in web development projects?

Accepted Answer

Technical SEO is always included: semantic HTML, correct heading hierarchy, meta tags, canonical URLs, Open Graph, structured data (JSON-LD), robots.txt, sitemap.xml, Core Web Vitals optimisation, and Google Search Console setup. Content SEO (keyword research, content strategy) is a separate service.

Question 26

How long does it take to see SEO results?

Accepted Answer

For technical SEO improvements (fixing crawl errors, improving Core Web Vitals), you can see indexing improvements within days. For organic ranking improvement on competitive keywords, expect 3–6 months. For domain authority growth via content and links, expect 6–12 months. SEO is a compounding investment, not a quick fix.

Question 27

Do you do content writing?

Accepted Answer

We do content strategy (keyword research, topic clustering, content briefs) and a limited amount of founding content. For ongoing content production at volume, we partner with specialist content agencies or help you build an in-house capability.

Question 28

Can you improve the SEO of an existing site?

Accepted Answer

Yes. We start with a technical SEO audit, identify the highest-impact issues, fix them, and then layer in content strategy. Most existing sites have 5–10 technical issues that are suppressing their rankings — fixing those first produces the fastest visible results.

Question 29

What kind of AI work do you actually do?

Accepted Answer

We build AI systems that solve specific operational problems: document processing and extraction, workflow automation, customer-facing chatbots (for appropriate use cases), predictive scoring, and custom LLM integrations into existing products. We do not build novelty AI features — we build systems that produce measurable operational improvement.

Question 30

Which AI models do you use?

Accepted Answer

Primarily OpenAI GPT-4o for general language tasks and structured outputs. Anthropic Claude for longer-context analysis. Embedding models (OpenAI Ada, Cohere) for semantic search and classification. Open-source models (Llama, Mistral) for on-premise deployments where data cannot leave your infrastructure.

Question 31

How do you ensure AI output quality?

Accepted Answer

Every AI system we build includes: structured output validation (Zod schemas against model responses), human review checkpoints for high-stakes decisions, comprehensive logging so you can audit every input and output, and accuracy benchmarking against a held-out test set before production deployment.

Question 32

Is my data used to train AI models?

Accepted Answer

No. We use API-based model access, not fine-tuning with your data. Your prompts and completions are never used to train any model. For maximum data control, we can deploy models on your own infrastructure using Ollama or similar.

Question 33

How do you communicate during a project?

Accepted Answer

We set up a shared Notion workspace for documentation and a Slack connect channel (or email if you prefer) for day-to-day communication. Weekly check-in calls are 30 minutes. We send a written progress update every Friday — no meeting required if things are on track.

Question 34

What is your response time during a project?

Accepted Answer

During active development, we respond to messages within 2–4 hours during business hours (9am–6pm UK time, Monday–Friday). We do not respond to non-urgent messages outside business hours — this protects the quality of the work.

Question 35

Do you work with clients in different time zones?

Accepted Answer

Yes. We have worked with clients across North America, Europe, the Middle East, and Asia-Pacific. We schedule check-in calls at times that work for your timezone, and async communication covers the overlap gaps.

Question 36

How do you handle sensitive data?

Accepted Answer

We apply the principle of minimum necessary access: we only collect, store, and process the data required for the specific task. Sensitive data is encrypted at rest (AES-256) and in transit (TLS 1.3). We never store credentials in code — only in environment variables or secret management systems.

Question 37

Do you sign NDAs?

Accepted Answer

Yes, we are comfortable signing mutual NDAs before the project starts. We take confidentiality seriously — we do not discuss client work with other clients, and we ask permission before including your project in our portfolio.

Question 38

Are you GDPR compliant?

Accepted Answer

Yes. Our own operations (this website, our communication tools) follow GDPR principles: minimal data collection, explicit consent where required, and data subject access rights honoured promptly. For projects we build for you, we design GDPR compliance in from the start rather than retrofitting it.

Question 39

Can you build HIPAA-compliant systems?

Accepted Answer

We can build systems that meet HIPAA technical requirements (encryption, access controls, audit logging). Full HIPAA compliance also requires administrative and physical safeguards that are your organisation's responsibility. We document the technical controls we have implemented so your compliance team can complete the full assessment.

Question 40

Which CMS do you use?

Accepted Answer

We match the CMS to the project. Sanity is our default for content-heavy sites (excellent developer experience, real-time collaborative editing). Contentful for enterprise clients already in that ecosystem. Payload CMS for projects that need CMS + backend in one. WordPress when the client has an existing WordPress environment and specific plugin requirements.

Question 41

Can non-technical people update the site?

Accepted Answer

Yes — this is a primary design requirement. We configure the CMS to show only the fields relevant to each content type, with clear labels and validation. We do not expose configuration that could break the site to non-technical editors.

Question 42

What are the ongoing CMS costs?

Accepted Answer

Sanity: free for up to 3 users, $15/user/month thereafter. Contentful: free tier available, paid plans from $300/month for larger teams. Payload CMS: open source, self-hosted — only infrastructure costs. We itemise CMS costs in every proposal.

Question 43

What performance targets do you aim for?

Accepted Answer

Lighthouse score ≥90 on all four categories (Performance, Accessibility, Best Practices, SEO). LCP < 2.5s on mobile. TBT < 200ms. CLS < 0.1. Core Web Vitals "Good" status on Google Search Console within 30 days of launch.

Question 44

How do you achieve high performance?

Accepted Answer

Static pre-rendering where possible (no server computation at request time). Self-hosted fonts (no Google Fonts round-trips). Images in WebP/AVIF with explicit dimensions (no layout shift). Third-party scripts deferred until idle. No layout shifts from ads or dynamic content. Aggressive CDN caching.

Question 45

What about sites with lots of images or video?

Accepted Answer

Images: we use next/image for automatic WebP/AVIF conversion, lazy loading, and explicit dimensions. Video: hosted on Cloudflare Stream or Mux (not self-hosted), which handles adaptive bitrate streaming. The hero video is represented by a static poster until user interaction — so LCP is from the poster, not the video.

Question 46

Can the site handle sudden traffic spikes?

Accepted Answer

Yes, if deployed on Vercel or a similar edge network. Static pages are served from edge nodes globally — they do not hit a single server. API routes scale automatically (serverless). For applications with database-heavy backends, we implement connection pooling and caching layers to handle spikes gracefully.

Question 47

What happens when you add a team member who needs to edit content?

Accepted Answer

CMS licences scale per user — you add them to the CMS workspace. The site itself does not need to change. For code contributors, we set up a development environment guide so new team members can get running within 30 minutes.

Question 48

Can the architecture support international expansion?

Accepted Answer

Next.js has built-in internationalisation support (routing, language detection, locale-based content). If you are planning international expansion, tell us at the start of the project — the architecture choices at the beginning are much easier to get right than to retrofit later.

Questions answered,
honestly.

About the Studio

Pricing & Investment

Timeline & Process

Ownership & Rights

Hosting & Infrastructure

Maintenance & Support

SEO & Content

AI Automation

Support & Communication

Security & Privacy

CMS & Content Management

Performance & Web Vitals

Scalability

Ask us directly.

Let's discuss your project.

Questions answered, honestly.