← Nurullah Cirit

Technical partner for your idea

You have a product idea but not the engineering background to judge how it should be built, what it will cost, or who should build it. I work with founders and idea owners to turn a concept into a clear technical plan, then help put the right team in place and lead it to delivery. I cover both software and hardware projects.

Discuss a project Email

Services

Feasibility analysis

Before you commit budget, find out whether the idea can be built, what the hard parts are, and what it will realistically take.

  • Technical viability and the main risks, with ways to reduce them
  • Build, buy, or integrate options for key components
  • Rough estimates of cost, timeline, and team size
  • Proof-of-concept work where a question can only be answered by trying it

Technical and implementation planning

A plan that an engineering team can execute and that you can use to talk to investors, partners, or vendors.

  • System architecture and technology choices, with the reasoning behind them
  • Scope for a first version, and what can wait
  • Milestones, deliverables, and a phased roadmap
  • Hardware considerations such as components, prototyping, and manufacturing path

Team building

Help finding and assembling the people who will build the product, whether in-house hires, freelancers, or an outside firm.

  • Defining the roles and skills the project actually needs
  • Writing role descriptions and running technical interviews
  • Evaluating agencies, contractors, and hardware vendors

Technical leadership

Ongoing leadership of the engineering team on your behalf, so you can focus on the business side.

  • Sprint planning, task breakdown, and progress tracking
  • Architecture decisions and code or design reviews
  • Regular, plain-language progress reports to you
  • Keeping scope, schedule, and quality in balance as the project changes

How it works

  1. Initial conversation. You describe the idea, your goals, and your constraints. We decide together what kind of help makes sense.
  2. Assessment. I look at feasibility and the main technical questions, then send you my findings and a recommendation.
  3. Plan. We agree on architecture, scope, milestones, and the team needed to deliver them.
  4. Build. I help assemble the team and, if you want, lead it through development to launch.

You can engage for a single step, such as a feasibility study, or for the whole project.

A good fit if you

Background

I'm a software and computer engineer with experience in embedded firmware, USB and machine-vision hardware, desktop and Android applications, and performance-critical C/C++ systems. That range lets me plan across the hardware and software boundary, where many projects run into trouble. More on my work and experience.

Tell me about your idea. The form takes a few minutes, and I'll reply to discuss next steps.

Discuss a project