Skip to main content

Sites where every claim has a reviewer.

For Boston biotech, healthcare and university-linked teams: websites that survive scientific and legal review, plus small internal tools.

10
Products built in-house
12
Web projects in the portfolio
04
Site languages: EN, TR, ES, DE
UTC+3
Overlaps US mornings and the full EU workday

A biotech or medical-device website in Boston passes through more hands than most: scientific staff, regulatory, legal, sometimes an investor. A single changed sentence can mean three approvals. A good build makes that cheap by separating claims from layout, so the words can change without touching the design.

Claims live in one place

We keep product and research claims in a content layer your team edits through an admin panel, each with an owner and a last-reviewed date. A reviewer opens one screen to see every claim on the site. Design stays untouched when a sentence changes, and the audit trail answers the question of who approved what.

Patient and participant data

Contact forms for patients or study participants raise questions a brochure site never does: what is collected, where it is stored, who reads it. Massachusetts has its own data security rules, and HIPAA may apply depending on your role. Your counsel decides the position. We build the form so it can be carried out, and we keep health data out of analytics tools.

Small tools for labs and clinics

Between the website and the enterprise system there are jobs no vendor covers: an equipment booking sheet, a sample request form, a referral inbox. These are small web apps with a login and a list. Our CRM panel and the appointment flow we built for a clinical psychologist show the level of detail we work at.

Eastern Time

Calls run 9 to 11 a.m. Eastern. The gap to Istanbul is seven hours in summer and eight in winter, the same as for New York.

Time difference with Boston

Boston hours against Istanbul

Time in the cityIstanbul, summerIstanbul, winterOn our side in summer
08:0015:0016:00Working hours, team online
10:0017:0018:00Working hours, team online
12:0019:0020:00Evening, handoff notes
15:0022:0023:00Offline, reply next morning
17:0000:00 (next day)01:00 (next day)Offline, reply next morning

How a project runs

From first conversation to launch

Read the full process
  1. Discovery

    We document the business goal, audience, available material, and technical constraints.

  2. Scope

    Pages, features, priorities, responsibilities, and review criteria are written down.

  3. Design

    We establish the interface, component rules, and a CSS design system when the project needs one.

  4. Development

    We implement the approved interface and connect the required panels, CRM functions, or messaging tools.

  5. Quality review

    We review mobile behavior, performance, core accessibility requirements, and technical SEO.

  6. Launch

    The approved release goes live with the agreed support period and content handoff.

Technology used in this work

  • Next.js
  • React
  • Tailwind CSS
  • TypeScript
  • Supabase
  • PostgreSQL
  • Structured US public datasets
  • Versioned data snapshots
  • Tested calculation engines
  • CSS Custom Properties
  • Design Tokens

Frequently asked questions

Can the site show the date each claim was last reviewed?

Yes. Each claim carries an owner and a review date in the admin panel, and the date can be shown on the page when you want it public.

Do you build HIPAA-compliant systems?

We build the application. Whether a given setup meets HIPAA depends on your agreements and your hosting, which your counsel and provider settle. We raise the questions that affect the build at scoping.

Can you make internal tools for a research group?

Yes, small ones: booking, requests, inventories and referral lists, with a login and an export.

Tell us what you need built.

Write the business, the market you sell to and what a visitor should be able to do. We reply with the questions that settle scope.

Chat