— Contact

Have a technical or product problem worth discussing?

Email is the best way to reach me. A few lines about what you’re working on is enough to start. No account, no booking form, no questionnaire.

Useful to include

  • Your name and, if relevant, your organisation
  • The nature of the project
  • A short description of the problem or goal
  • An existing website or reference link, if there is one

What happens next

  1. 1 I read every enquiry and reply personally.
  2. 2 If the project looks like a good fit, we talk it through.
  3. 3 If we’re both interested, a short structured discovery process follows.

— Independent work

What I take on

Alongside Polynovea, I take on a limited number of independent engagements, selected by relevance, scope, feasibility and availability. Work may be project-based or structured as ongoing advisory, with terms agreed upfront.

  1. A

    Websites & digital platforms

    Purpose-built business and product websites, CMS-backed experiences, digital platforms, integrations and deployment.

  2. B

    Fractional CTO & technical leadership

    Part-time technical leadership for founders and growing teams: architecture decisions, engineering roadmaps, technology selection, team and vendor reviews, and delivery oversight within agreed commitments.

  3. C

    Product & systems architecture

    Product diagnostics, technical audits, system design, integration architecture, workflow planning, feasibility assessments and implementation blueprints.

  4. D

    Applied AI/ML & automation

    AI feasibility, model integration, intelligent workflows, automation and focused AI/ML implementations designed around real operational needs.

Independent engagements are with me personally and are separate from Polynovea. Polynovea’s code, designs, data and systems are never used, shared or recreated in client work, and I don’t build competing versions of its products.

— How a project starts

Understand the organisation before designing anything

Once we've agreed there's a fit, every engagement starts with a short three-part discovery. You don't design the solution. You tell me what people need to achieve and what your team has to run, and I recommend the structure and the technical approach. Short answers are fine, and so is “not sure, I'd like your recommendation”.

The principles behind these questions →

  1. 01

    Business & Organisation

    What the organisation actually does, why it exists, who decides, what it offers today and what is only planned.

  2. 02

    Brand & Audience

    How it should feel, what must stay recognisable, what visitors should never feel, and how much creative freedom there is.

  3. 03

    Website & Digital Experience

    The single most important job of the site, what the team updates, the systems already in place, and what search and AI assistants must understand.

A few of the questions, and why I ask them

  • “What is planned, but not available yet?”

    So future plans are never presented as current capabilities.

  • “Who makes the final decision to buy or work with you?”

    The user and the decision-maker are often different people, and the site has to serve both.

  • “What alternatives do people consider instead of you?”

    Including doing it manually or doing nothing. That is the real competition.

  • “What should you never become?”

    Often more useful than knowing what you want to become.

  • “What does your team repeatedly create or update?”

    This decides whether you need a CMS at all, and what it should manage.

  • “What should search engines and AI assistants clearly understand about you?”

    Discoverability is designed in from the start, not bolted on after launch.

— Questions

Common questions

What does a fractional CTO engagement include?

Part-time technical leadership for founders and growing teams: architecture decisions, engineering roadmaps, technology selection, team and vendor reviews, and delivery oversight within agreed commitments. It can run as ongoing advisory or around a specific milestone.

Do you build websites?

Yes. Purpose-built business and product websites, CMS-backed experiences and digital platforms, designed for search and for AI answer engines. I designed and shipped polynovea.in, infrakinetic.in and careers.infrakinetic.in.

How do you build software?

I design the system, covering architecture, product design and UI/UX, and Claude writes the code, working to the contracts and evidence standards I set. That is how I ship platform-scale systems such as Infrakinetic, an enterprise business operating system with 29 engines.

What kinds of AI and machine learning work do you take on?

AI feasibility assessments, model integration, intelligent workflows, automation and focused AI/ML implementations designed around real operational needs, with deterministic fallbacks and human review where decisions matter.

How do engagements start, and how are they priced?

Email me at subrojitroy@polynovea.in with a short description of the problem. If there is a fit, a short structured discovery follows. Work is project-based or ongoing advisory, with scope and terms agreed upfront.

Are independent engagements part of Polynovea?

No. Independent engagements are with me personally. Polynovea's IP, code, data and systems are never used or recreated for clients, and I don't build products that compete with Polynovea's.