roboticsfrontier مؤسسه پژوهش‌های مرزی رباتیک
Menu

Sheet 05 — Work with us · Rev D

Four ways to collaborate. Start with a conversation.

This page exists to help you decide whether to send it. If your problem is not manipulation, we will say so and point you somewhere better.

  • Pathway A

    Academic partnership

    For: research groups with an overlapping question. What happens: joint work toward co-authored publications — remote by default, visits in either direction. You get: a partner lab with hands on real hardware and agreed data- and code-sharing.

    Typical shape — paper-sized

  • Pathway B

    Contract research

    For: companies with a handling step that fails. What happens: scoping call → feasibility study with a written answer → project with acceptance criteria. You get: a clear yes-with-plan or a reasoned no, in writing, before you commit.

    Feasibility first, always

  • Pathway C

    Consulting

    For: teams that need a review, not a project — a gripper selection, a cell design, a failure analysis. What happens: short engagement, written findings. You get: an answer sized to the question, from someone who has published on it.

    Days to weeks

  • Pathway D

    Prototype development

    For: a validated feasibility result that needs to become hardware. What happens: statement of work — deliverables, dates, acceptance criteria — then build and bench test. You get: a working prototype and the documentation to take it further.

    Follows a feasibility study · never skips it

Start the conversation

Choose a personal contact and introduce your project by email.

Worth including:

  • the problem in one paragraph
  • constraints: hardware, environment, timeline
  • what a good outcome looks like

Choose a recipient below. Your email app opens with these questions ready to answer: who you are, which pathway fits, the problem, its constraints, and what a good outcome looks like.