Question 1

When was beynart founded?

Accepted Answer

beynart was founded as a multi-layer partnership bringing together digital marketing and enterprise software disciplines. We started with a team carrying 10+ years of practice across strategy, brand, MarTech, and enterprise systems. Legal name: beynart Pazarlama Yazılım Teknolojileri A.Ş.

Question 2

How big is the team?

Accepted Answer

The team is built around four disciplines: strategy & research, design & brand, MarTech & AI engineering, enterprise software. Per active engagement we assign a 3–8 person project crew; partner-level ownership is on every engagement. Capacity scales through a long-standing network of specialist freelancers — co-workers, not subcontractors.

Question 3

Where are your offices?

Accepted Answer

We work out of two offices in Istanbul, Türkiye. The main office is in Levent (Kolektif House Levent, Talatpaşa Cd. No: 5/1 Office No: 8, Şişli) — for client meetings and hybrid work. The second is at Khas Teknopark (Kadir Has University Teknopark, Cibali, Fatih) — for R&D-heavy crews. The team is also remote-friendly; international clients run fully async with us.

Question 4

Which sectors do you work with?

Accepted Answer

We're a sector-agnostic partnership, but we go deep in: SaaS / software, e-commerce & retail, fintech & banking, industry & manufacturing, professional services, media, education, and healthcare. Regulation and customer behavior shift by sector; we adapt the discipline to the sector instead of forcing one model on everyone.

Question 5

What languages do you work in?

Accepted Answer

Turkish and English. All documentation, decisions, and code comments are kept in the preferred language. If your client has multilingual leadership, we ship parallel outputs. A third-language need (German, Arabic, Russian) goes through a professional translation partner; we don't generate it in-house.

Question 6

How do reference and credit policies work?

Accepted Answer

In the first week we sign a reference policy document: which client logo can be shared on which channel, which case study is cleared for publication. Nothing is shared without client approval. NDA can be signed before the first discovery call as standard; for substantial work we prefer a mutual NDA, not one-way.

Question 7

Who founded beynart and runs leadership?

Accepted Answer

The founding team brings 10+ years of experience across strategy, engineering, and brand. Every engagement gets partner-level ownership — meaning the signature on the contract also sits at the weekly review table. Detailed CVs are shared on the discovery call; public LinkedIn profiles are reachable from the social links in the footer.

Question 8

How does pricing work?

Accepted Answer

Three models: sprint engagement (fixed scope, fixed price), retainer (monthly fixed), partnership (master agreement + sub-package). Sprint prices typically run USD 25K–200K; retainers run USD 8K–60K per month. Scope, team size, and duration adjust to the case. After NDA we share a budget range tailored to your project. We don't price by the hour.

Question 9

Do you sign NDAs? How?

Accepted Answer

Yes — before and after the first discovery call. We have a standard mutual NDA template; if you prefer, we work with yours (small revisions are usually needed). With NDA in place, we open up budget ranges, client references, and detailed case examples. Term is typically 3 years; can extend by topic.

Question 10

What does the contract structure look like?

Accepted Answer

Two layers: a master agreement plus per-engagement SOWs (statement of work). The master covers IP, confidentiality, liability, and termination. The SOW lays out scope, schedule, payment plan, and KPIs for each engagement. We work under Turkish law; for international clients we use English or Dutch law when it makes sense.

Question 11

What are payment terms?

Accepted Answer

Sprint engagements: 30% kickoff + 40% mid-point + 30% hand-off. Retainer: monthly upfront, closed at month-end with the report. All payments accepted in TRY, EUR, or USD; the FX-cut date is set in the contract. Late payment beyond a 15-day grace incurs 2% monthly interest — but this clause triggers near zero in any 12-month window.

Question 12

How do you work with third-party stakeholders?

Accepted Answer

Three models by need: (1) beynart as prime contractor — other vendors coordinate under us, the client signs once; (2) client as prime, beynart as subcontractor — running parallel to another agency; (3) co-vendor on equal footing — both sides report directly to the client. Choice depends on scope and the client's organization.

Question 13

How does an engagement end?

Accepted Answer

Two ways: natural close (hand-off + documentation at SOW end) or 30-day notice early exit (either side). In both cases, all working files, source code, runbooks, and transition notes go to the client. We don't do 'hostage data' — the day the engagement ends, the system runs in your hands.

Question 14

What if scope changes mid-engagement?

Accepted Answer

Sprint scope is frozen; new needs roll into the next sprint. In retainer, monthly scope is updated and decided at month-start. Major scope shifts (affecting 20%+ of budget) trigger a written change order; small revisions are approved in the weekly review. No surprise invoices.

Question 15

Which of the four layers should I start with?

Accepted Answer

Depends on context. If brand recognition is weak or repositioning is needed, start with Brand & Experience. If marketing spend is in motion but attribution is unreliable, MarTech & AI. If leadership is unsure 'what should we do next,' Strategy & Insight. If old ERP or legacy systems are slowing operations, Enterprise Systems. We narrow the entry layer together in the discovery call; most engagements start with 1–2 layers and expand over time.

Question 16

Do you do everything, or specialize in one area?

Accepted Answer

Deep expertise across all four layers — but we don't do everything inside every layer. For example, medical-device regulatory work, financial modeling, or legal counsel — we recommend the right partner and coordinate, but we don't deliver those ourselves. 'One partner, four layers' = one signature for coordinated work; not infinite scope.

Question 17

How is the build-vs-buy decision made?

Accepted Answer

Per business process, separately. For sector-standard work (accounting, HR, simple CRM), off-the-shelf SaaS — Logo, NetSuite, BambooHR, HubSpot. For processes that produce competitive edge (custom order flow, B2B portal, product configurator), custom software. In Discovery we run a TCO + flexibility + 3-year projection per process; the recommendation is based on those numbers, not on intuition.

Question 18

Advisory only, or do you also execute?

Accepted Answer

Both advisory and execution. A strategy doc on its own produces little value if it's not implemented. So our typical engagement structures as strategy + infrastructure + operations. For clients who specifically want 'advisory only,' we offer a quarterly review model — but it's rarely picked, because keeping the directing crew and the building crew aligned makes a measurable difference.

Question 19

We already have a partner on one layer — can we still work with you?

Accepted Answer

Yes. In the equal-footing co-vendor model we run parallel to the other agency; both sides report directly to the client. Three things matter: (1) clear boundaries (who owns what), (2) a weekly trilateral review, (3) an orchestration owner on the client side. This setup, when it lands well, delivers the most successful long-term partnerships — complementary, not competitive.

Question 20

Are you tech-agnostic, or do you prefer a specific stack?

Accepted Answer

Tech-agnostic — but we have preferences. Frontend: Astro, Next.js, React, TypeScript, Tailwind. Backend: Node.js, Python, Postgres, Redis. Cloud: AWS, GCP, Cloudflare. MarTech: HubSpot, Customer.io, Segment, n8n, Make. AI: OpenAI, Anthropic, LangChain, custom fine-tunes. If your stack uses something else (e.g., Vue, .NET, Azure), we work with it; we don't argue, we use the proven path.

Question 21

How do you use AI in operations?

Accepted Answer

AI as part of the operation, not a chat window. Live in production: customer interview synthesis (LLM), churn scoring (XGBoost), demand forecasting (Prophet), personalization (vector embeddings), content drafts, ticket triage, sales sequencing. Every AI workflow runs with human-in-the-loop approval; the team always sees what it approved. AI accelerates the hypothesis 10×; the decision stays with the human.

Question 22

How is AI data security handled?

Accepted Answer

Three principles: (1) PII gets hashed or tokenized before leaving for AI services; (2) Customer data is sent through no-training endpoints or self-hosted models so it never enters a public LLM training set; (3) All AI agent outputs are logged and auditable. KVKK / GDPR-compliant data inventory is prepared on every engagement; DPIA documents on request.

Question 23

Is KVKK / GDPR compliance your responsibility?

Accepted Answer

The compliance baseline of the systems we design is our responsibility. Data processing inventory, retention policy, consent management, server-side hashing, breach detection — embedded into the architecture. Legal opinion and regulatory reporting belong to your legal counsel; we have law firms we've worked with for years and can recommend on request. Holistic compliance is shared.

Question 24

Open source or closed source delivery?

Accepted Answer

All engagement outputs live in the client's GitHub or GitLab organization — as code the client owns, either open-source or internal. No vendor lock-in. beynart's own open-source libraries (e.g., astro-icon helpers, n8n templates) ship under MIT; they get used in client work, but the client can also fork them.

Question 25

Do you do mobile (iOS/Android) development?

Accepted Answer

We don't run native mobile development (Swift/Kotlin) in-house; we coordinate with a partner studio that owns that depth. Cross-platform projects on React Native and Flutter run on the in-house team. PWAs (progressive web apps) — when they fit, which is most B2B use cases — are built in-house.

Question 26

How do you measure outcomes?

Accepted Answer

Each engagement opens with 1–3 KPIs and a baseline measurement. KPI choice varies by layer: brand uses recall, NPS, price premium, recognition; MarTech uses MER, attribution quality, lead-to-close speed; strategy uses decision time, experiment count, channel performance; enterprise systems use uptime, latency, user productivity. Sprint-end comparison happens every cycle; monthly reviews track the trend.

Question 27

What are typical KPIs?

Accepted Answer

Some recurring targets: marketing efficiency (MER) up 30–60%, MarTech stack cost down 25–40%, manual workload down 30–50%, post-launch NPS +8 points, unit margin up 15–40%, license cost down 30–50%, decision time from 6 months to 2–4 weeks. But every engagement is measured from its own starting point; the number alone isn't the point — the delta is.

Question 28

How does hand-off work?

Accepted Answer

Every engagement runs with an 'enable' goal — at contract end, the client should be able to keep going on their own. The hand-off package includes: working code (source + infrastructure-as-code), runbooks, ADRs (architecture decision records), user training (live + recorded), knowledge base (Notion or internal wiki), and a 30/60/90-day transition plan. Hand-off is real — the day the engagement ends, your team can run the system.

Question 29

Is there support after the engagement ends?

Accepted Answer

Three models: (1) natural close (hand-off + 30-day soft-landing support), (2) advisory retainer (1–2 hours of advice per month + quarterly review), (3) return to a full retainer (operations continuation). The choice is set at contract time, but always changeable. We don't operate on a 'never call us again' model; long-term relationships are standard, return-to-retainer is common.

Question 30

How fast do you see results?

Accepted Answer

By the end of the first sprint (4 weeks) there is a clear decision input or output. Meaningful KPI improvement starts between weeks 8–12 — especially in MarTech and strategy layers. In brand work, NPS and price premium become measurable 90 days post-launch. In enterprise software, operational gains arrive as soon as the MVP enters production (8–14 weeks). We don't promise overnight wins; outcomes compound like interest.

Answers