Question 1

When was beynart founded?

Accepted Answer

beynart was founded in Istanbul in 2023 as a multi-layer partnership bringing together digital marketing and enterprise software disciplines. The founder and team set out with more than a decade of practice across strategy, brand, MarTech, and enterprise systems. Our legal name is beynart Pazarlama Yazılım Teknolojileri A.Ş.

Question 2

How big is the team?

Accepted Answer

The team is built around four disciplines: strategy and research, design and brand, MarTech and AI engineering, enterprise software. Each active engagement gets a 3 to 8 person project crew, with partner-level ownership on every one. When extra capacity is needed, we scale through a long-standing network of specialist freelancers. They work as co-workers, not subcontractors.

Question 3

Where is your office?

Accepted Answer

Our office is in Levent, Istanbul: Kolektif House Levent, Talatpaşa Cd. No: 5/1 Office No: 8, Şişli. We use it for client meetings, hybrid work, and the whole team. We're also comfortable remote; international clients run fully async with us.

Question 4

Which sectors do you work with?

Accepted Answer

We're sector-agnostic, but we go deep in a few areas: SaaS and software, e-commerce and retail, fintech and banking, industry and manufacturing, professional services, media, education, and healthcare. Regulation and customer behavior shift by sector, so 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 your preferred language. If your leadership is multilingual, we ship parallel outputs. A third-language need (German, Arabic, Russian) goes through a professional translation partner; we don't produce 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, and which case study is cleared for publication. Nothing is shared without your approval. An NDA can be signed before the first discovery call as standard; for substantial work we prefer a mutual NDA, not a one-way one.

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. 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 (fixed scope, fixed price), retainer (monthly fixed), and partnership (master agreement plus sub-packages). Sprint prices typically run USD 25K to 200K; retainers run USD 8K to 60K per month. Scope, team size, and duration adjust to the case. After an 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 or after the first discovery call, whichever you prefer. We have a standard mutual NDA template; if you'd rather use yours, we work with it, and small revisions are usually enough. With an NDA in place, we open up budget ranges, client references, and detailed case examples. The term is typically 3 years and can extend by topic.

Question 10

What does the contract structure look like?

Accepted Answer

Two layers: a master agreement plus a per-engagement SOW (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 percent at kickoff, 40 percent at mid-point, 30 percent at hand-off. Retainers: monthly upfront, closed at month-end with the report. Payments are accepted in TRY, EUR, or USD; the FX-cut date is set in the contract. Late payment beyond a 15-day grace period carries 2 percent monthly interest. In practice, this clause almost never triggers.

Question 12

How do you work with third-party stakeholders?

Accepted Answer

Three models by need. In the first, beynart is the prime contractor: other vendors coordinate under us, and you sign once. In the second, you are the prime and beynart works as a subcontractor, in parallel with another agency. The third is an equal-footing co-vendor model: both sides report directly to you. The choice depends on scope and how your organization runs.

Question 13

How does an engagement end?

Accepted Answer

Two ways: a natural close at the end of the SOW (hand-off plus documentation), or an early exit with 30 days' notice, available to both sides. In both cases, all working files, source code, runbooks, and transition notes go to you. We don't hold data hostage. 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 a retainer, scope is updated at the start of each month. Changes that affect more than 20 percent of the budget go through 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

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

Question 16

Do you do everything, or specialize in one area?

Accepted Answer

We carry deep expertise across all four layers, but we don't do everything inside every layer. Medical-device regulatory work, financial modeling, or legal counsel, for example: we recommend the right partner and coordinate, but we don't deliver those ourselves. One partner, four layers means 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 makes sense: 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, and 3-year projection per process. The recommendation rests on those numbers, not on intuition.

Question 18

Advisory only, or do you also execute?

Accepted Answer

Both. A strategy document that never gets implemented produces very little value on its own. So our typical engagements are structured as strategy plus infrastructure plus operations. For clients who specifically want advisory only, we offer a quarterly review model, but it's rarely picked. Keeping the directing crew and the building crew the same 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, and both sides report directly to you. Three things matter: clear boundaries (who owns what), a weekly trilateral review, and an orchestration owner on your side. When this setup lands well, it produces the longest-running partnerships we have. Complementary, not competitive.

Question 20

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

Accepted Answer

Tech-agnostic, but with 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 (say Vue, .NET, or 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 is 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, and the team always sees what it approved. AI speeds up the hypothesis tenfold; the decision stays with a human.

Question 22

How is AI data security handled?

Accepted Answer

Three principles. PII gets hashed or tokenized before it leaves for any AI service. Customer data flows through no-training endpoints or self-hosted models, so it never enters a public LLM training set. And all AI agent outputs are logged and auditable. A KVKK and GDPR-compliant data inventory is prepared on every engagement, with 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, and breach detection are 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 one on request. Holistic compliance is shared.

Question 24

Open source or closed source delivery?

Accepted Answer

All engagement outputs live in your GitHub or GitLab organization, as code you own, kept open-source or internal as you choose. No vendor lock-in. beynart's own open-source libraries (astro-icon helpers, n8n templates) ship under MIT; they get used in client work, and you can fork them too.

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 fit most B2B use cases, and those are built in-house too.

Question 26

How do you measure outcomes?

Accepted Answer

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

Question 27

What are typical KPIs?

Accepted Answer

Some recurring targets: marketing efficiency (MER) up 30-60 percent, MarTech stack cost down 25-40 percent, manual workload down 30-50 percent, post-launch NPS up 8 points, unit margin up 15-40 percent, license cost down 30-50 percent, 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 toward one goal: at contract end, your team can keep going on its own. The hand-off package includes working code (source plus infrastructure-as-code), runbooks, architecture decision records, live and recorded user training, a knowledge base (Notion or an 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: a natural close (hand-off plus 30 days of soft-landing support), an advisory retainer (1 to 2 hours of advice per month plus a quarterly review), or a return to a full retainer (operations continue). The choice is set at contract time but can always change. We don't operate on a never-call-us-again model; long-term relationships are our standard, and returning to a retainer is common.

Question 30

How fast do you see results?

Accepted Answer

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

Answers