Frequently Asked Questions

We are a Wisconsin software company focused on two lanes: custom development services (analysis, architecture, delivery planning, and build) and purpose-built products for schools, academies, and operators (including GuruVidyaZen / SISLMS, Saarthee apps, and related tools). See Services and our product pages for details.

Both, depending on the engagement. Many clients hire us to design and ship a system tailored to their workflow. We also operate and evolve our own products. This FAQ is about how we run projects-not product pricing tiers or feature matrices. Product-specific questions belong on the product page or a scoped demo conversation.

Saaniya Software LLC is a U.S. (Wisconsin) company. We work with organizations globally via direct contracts and marketplaces such as Upwork. Communication is typically async-first with scheduled checkpoints.

Strong fits: cloud web apps, education / academy operations tools, ops and fleet-style workflows, integrations, and greenfield builds where requirements need clarifying. We decline HIPAA / PHI and regulated medical-financial processing without a separate written compliance program-see our Terms.

We use a phased path that stays visible to you:

1. Discovery: goals, constraints, success criteria, and risk notes
2. Architecture: stack, data model, security boundaries, and integration map
3. Delivery plan: milestones, Done-when checks, and out-of-scope list
4. Build: iterative implementation with reviewable increments
5. Verify: automated and/or manual checks against the agreed Done-when
6. Ship: preview deploy, then production when you approve

You approve the plan and stop rules; we do not "wander" into production without a clear gate.

HOTL (Human-on-the-Loop) means a human architect approves the plan and hard stop rules once, then an AI agent can execute until Done or Blocked-without asking for permission on every micro-step. Secrets, destructive data changes, and ambiguous cross-system work still force a human stop. Read more on our HOTL page.

Every work package restates Plan, Done when, and Out of scope. New ideas become a follow-on package instead of silent scope creep. If a Done-when check fails twice, we stop and ask a precise question rather than guessing.

Expect short status updates tied to milestones: what changed, evidence (build/tests/URLs), and residual risks. For marketplace jobs we follow the platform's messaging norms; for direct clients we agree on a channel (email, ticket hub, or shared doc) at kickoff.

We work iteratively with frequent reviewable increments. Formal two-week ceremonies are optional-what matters is a written plan, demoable progress, and verification before release. Small fixed-scope jobs may be one or two packages; larger programs are sequenced milestones.

Start with a short discovery conversation or written brief: problem, users, constraints, and deadline. We respond with a proposed scope, assumptions, and either a fixed package or a phased estimate. You can contact us, request a product demo, or engage via Upwork.

We prefer clear packages when requirements are stable (fixed scope + Done-when). Hourly or retainer fits exploration, ongoing product work, or changing priorities. Marketplace catalog packages follow published Upwork terms; custom SOWs spell out milestones and acceptance.

A decision-maker for scope questions, access to examples or systems you want integrated, and timely feedback on demos. Unclear ownership of requirements is the #1 delay-we will flag gaps early rather than invent them.

Small, well-scoped builds can land in days to a few weeks. Multi-module systems (auth, data model, roles, integrations, production hardening) are usually multi-milestone. We estimate after discovery-not from a one-line ask.

Yes. We can join an existing GitHub/Vercel stack, follow your branch rules, and leave documentation so your team can continue. We ask for a short onboarding pack: repo access, environments, coding standards, and who approves merges.

Common stack for our products and many client builds: modern TypeScript/React front ends, serverless or Node APIs, managed Postgres (e.g. Supabase/Neon), and Vercel-style hosting. We choose tools for maintainability and your constraints-not for novelty alone.

LLMs accelerate drafting, refactors, tests, and documentation inside governed agent workflows (for example Cursor agents with project rules and HOTL skills). Humans still own architecture, security-sensitive steps, acceptance, and production release. See HOTL + AI development.

We do not use customer content to train public foundation models unless a written order says so. Tooling is configured to disable vendor training on customer inputs where the vendor offers that control. Details: Privacy Policy and Terms.

Yes where the project supports it: local verify (build / tests), preview deploys, then production promotion with recorded SHAs and URLs. Automation never skips human approval for production when your rules require it.

Custom deliverables follow the SOW or marketplace contract. Saaniya Software retains pre-existing libraries, frameworks, and product IP. Your data and content remain yours. We document what is licensed vs. assigned at handoff.

Least-privilege access, secrets kept out of git, TLS in transit, and environment separation (preview vs production). Education products follow school-as-controller / processor practices when under a school agreement-see Education Privacy. We do not claim SOC 2 at launch.

We can work under a mutual NDA and a short MSA/SOW for direct clients. Marketplace jobs also follow the platform's terms. Send your template early so legal review does not block kickoff.

Yes-explore GuruVidyaZen / SISLMS, Saarthee products, and others from the site navigation. Product demos and pilots are separate from custom SOWs. Use Request Demo for product walkthroughs.

Often yes, as a scoped services engagement on top of the product base-configuration, integrations, or net-new modules. We will say clearly when a request is better as a separate custom app.

1. Send a short brief via Contact or open a marketplace job
2. Align on Plan / Done when / Out of scope
3. Kick off discovery or a fixed package
4. Review a preview build, then approve production

Email saaniyasoftware@nasneeraj.com or use the contact form. For product trials, use Request Demo.