# Futura Research

> Custom software systems, internal tools and applied AI for companies that need the work to actually ship.

Futura Research is a software studio based in Kerala, India. We design and ship
custom software: customer-facing products and platforms, internal management
systems, dashboards and analytics layers, and applied AI features. Clients
retain full intellectual property ownership, and work is delivered documented
and containerised with no vendor lock-in.

Primary backend: Ruby on Rails. Python/FastAPI where the task suits it, Node.js
as a second option. Next.js and TypeScript on the interface layer.

Contact: signal@futura-research.com
Start a project: https://futura-research.com/get-started

## Pages

- [Custom Software Systems & Product Engineering](https://futura-research.com): Product development, management systems, data and analytics, and applied AI. Overview of what Futura Research builds and how engagements work.
- [Selected Work](https://futura-research.com/work): Shipped products, platforms and websites: KonexZero (realtime communication APIs), WAVBEE (music distribution platform), Euclidean Technologies and Teralis (corporate sites).
- [Capabilities](https://futura-research.com/capabilities): Product engineering, cloud architecture, applied AI and venture architecture. Technology stack, engagement models and delivery standards.
- [Ventures & Internal Labs](https://futura-research.com/ventures): Internal tools built and used before they are offered to anyone: SaaSable, LaunchPad Kit, Handover, Pulseboard, AuroraSpec and TimeSync — plus what we shut down and why.
- [For Startups — Engineering as Investment](https://futura-research.com/startups): Build the product before you raise. Futura Research builds at a reduced rate, or none, in exchange for a stake, contributing engineering and infrastructure as the investment. How it works, what we look for, and who owns the result.
- [Partner Ecosystem](https://futura-research.com/ecosystem): Futura owns the engineering; specialist partners cover brand, design, growth, infrastructure and electronics. What each discipline covers, and how delivery is split on a typical launch.
- [Start a Project](https://futura-research.com/get-started): Structured project brief: company context, users, current setup, bottleneck, desired outcome and timeline. Initial response within 24–48 hours.
- [Contact](https://futura-research.com/contact): General inquiries, partnerships, existing-project follow-ups and advisory questions. Reply window 24–48 hours.

## For startups

Engineering as investment: Most early founders need a product before they can raise, and need money before they can build the product. We take the other side of that trade: we build it, and take a stake instead of an invoice.

Full terms: https://futura-research.com/startups

## Services

- **Product Development**: Customer-facing platforms, partner portals, SaaS products and communication-heavy tools built for real usage and long-term maintainability.
- **Management Systems**: Software for employee operations, logistics, customer management, approvals and day-to-day coordination that breaks down across spreadsheets and scattered tools.
- **Data & Analytics**: Dashboards, reporting layers and analytics systems that help teams understand operations, performance and what needs attention next.
- **Applied AI**: Assistants and chatbots grounded in your own documents, knowledge-base search that returns sourced answers, AI-assisted analytics, and model APIs integrated into existing products.
- **Cloud Architecture**: Containerised infrastructure on AWS, Azure, GCP or bare metal, with CI/CD pipelines that make delivery repeatable. Rails-first backends, with Python or Node.js where a task genuinely calls for them.
- **Venture Architecture**: Technical due diligence for founders: execution roadmaps, build-versus-buy analysis and feasibility studies before budget is committed.

## Common questions

- **What does Futura Research do?** Futura Research designs and ships custom software: customer-facing products and platforms, internal management systems, dashboards and analytics layers, and applied AI features. Engagements run from scoping through to production and ongoing iteration.
- **What kinds of projects do you take on?** Product development, management and operations systems, dashboards and analytics, applied AI features, communication tools, and upgrades to existing systems that need a stronger architecture or cleaner workflows. The common shape is a system with real users and real workflow complexity behind it.
- **How do you work with clients?** Three ways. A fixed-scope build: you describe the outcome, we build it for a fixed price and hand over the complete codebase. An ongoing product build: we run engineering for a product over time, accountable for what ships. Or a partner build, for startups: we work at a reduced rate in exchange for a stake, contributing engineering and infrastructure as the investment. In all three we prefer to work as product owners rather than as extra hands: involved in the decisions about what gets built, and accountable for what ships.
- **What AI work do you do?** Applied AI inside real products: assistants and chatbots grounded in a company’s own documents, knowledge-base search that returns sourced answers, and AI-assisted analytics and summarisation. We integrate model APIs into existing systems rather than rebuilding around them, and we say so when a problem is better solved without a model.
- **What technologies do you use?** Ruby on Rails is our primary backend. Python and FastAPI come in where the task suits them, and Node.js is a second option when it makes a job simpler. On the front end we use Next.js and TypeScript. Data and background work run on PostgreSQL, Redis and Sidekiq; delivery is Docker with GitHub Actions to AWS, Azure, GCP or bare metal; AI features use LLM APIs with retrieval pipelines.
- **How do you structure an application?** Three shapes, chosen by how complex the interface is. A Rails monolith with Inertia.js when the app is cohesive and we want a single deployable without giving up a modern front end. Rails as an API with a separate Next.js front end when the interface is heavy or needs to ship on its own cadence. And a straight Rails monolith with server-rendered views when the interface is simple enough not to need more. Rails is the backend in all three; the decision is about the front end, not the foundation.
- **How much does a project cost?** Projects start at around ₹1,00,000 (roughly $1,100) and scale with complexity. A fixed-scope build is priced before it starts, so you know the number in advance. For startups we also work at a reduced rate in exchange for a stake. The first reply to a brief includes a budget range or the questions we need answered to give one.
- **What do you not take on?** Work that does not need engineers. WordPress and Shopify theme builds, page-builder sites, and anything a non-developer could assemble from a tutorial — we would only be charging you for something you can do yourself. What we take on is work we can own and execute end to end.
- **Can you build for equity instead of a fee?** For startups, yes. We build at a reduced rate — sometimes none at all — in exchange for a stake, contributing the engineering and infrastructure as the investment. Ownership is shared on terms agreed before work starts. We are selective: we look for founders working on this full time and a problem we can understand without a deck. The full terms are on the For Startups page.
- **How large is your team?** A core team, with vetted developers we have worked with before who join as a project needs them. Capacity scales to the engagement rather than the engagement being trimmed to fit whoever is free.
- **Can you take over an existing codebase?** Yes. We start with a short audit that produces a written assessment of the code, the infrastructure and the risks, plus a plan for what to do about them. You can act on that plan with us or with anyone else — it is yours either way.
- **What happens after launch?** Either an ongoing product build keeps it moving, or we hand over: repository, documentation, Docker build, CI pipeline and infrastructure credentials. Nothing we build depends on a service that only we can run, so a handover is a real option rather than a threat.
- **How long does a project take?** A contained module, dashboard or internal tool runs as a six-to-eight-week fixed-scope build. A new product starts with a scoping phase, then builds in increments so something is in front of users early. We do not put a delivery date on a build before understanding the users, the workflow and the integrations.
- **Where is Futura Research based?** Kerala, India, working with clients remotely since 2015. Time zone is UTC+05:30, which overlaps a full working day with Europe and the Gulf and the morning with US Eastern.
- **Who owns the code you write?** You do, in the normal case: work is delivered fully documented and containerised, with no vendor lock-in and the complete codebase handed over. On partner builds with startups, ownership is shared on terms agreed before anything is written. Either way it is settled in the commercial agreement up front, never left ambiguous at handover.
- **How do I start a project?** Send a brief through the Start a Project page covering company context, who the users are, your current setup, the bottleneck and the outcome you want. Initial response is within 24–48 hours, with either follow-up questions or a clear next step.

## Optional

- [Full site content](https://futura-research.com/llms-full.txt): every page's content as plain Markdown.