Content infrastructure
#1Content injectionDetails
Injection of final copy supplied by the client into the site shell. We integrate text the client has already written, reviewed, and signed off on; we do not author, translate, edit, or strategize copy.
#2Multilingual i18n architectureDetails
Setup of multilingual routing, message-file structure, and locale switcher. Translation of the actual content into additional languages is excluded; the client supplies translated copy per locale.
#3Headless CMS / blog setupDetails
Provisioning of a headless CMS workspace and schema definition (Sanity, Hygraph, or equivalent). Authoring posts, editorial calendars, and ongoing content production are excluded.
#4Legal pages scaffoldDetails
Scaffolding of legal pages (terms, privacy policy, cookie policy, disclaimers) from final text supplied by the client or the client's lawyer. We do not draft or provide legal text.
#5Technical SEO infrastructureDetails
Technical-SEO infrastructure: sitemap.xml, robots.txt, canonical tags, hreflang, structured-data (JSON-LD) wiring, and OpenGraph/Twitter metadata bindings. Keyword research, content strategy, off-page SEO, and link-building are excluded.
#6Media delivery infrastructureDetails
Wiring of media-delivery primitives (next/image components, CDN binding, lazy-loading helpers, blur placeholders). Sourcing, shooting, editing, or licensing the media itself is excluded.
#42Copywriting authorshipAnchor
Copywriting authorship is excluded from engineering scope. SessDev only integrates final copy supplied and approved by the client. Writing, rewriting, tone definition, and editorial strategy remain the client's responsibility unless separately quoted and approved.
#43Translation / localization serviceAnchor
Professional translation and localization are excluded from base scope. SessDev provides i18n infrastructure (routing, locale wiring, message structure), but language conversion, cultural adaptation, and linguistic QA are client-side services unless separately contracted.
Brand-asset injection
#7Brand asset injectionDetails
Injection of final brand assets (logo, favicon, OG image, app icons) supplied by the client in production-ready formats. Logo design, brand-mark creation, and asset retouching are excluded.
#8Color-token setupDetails
Setup of color tokens in Tailwind / CSS variables from the palette supplied by the client. Defining the palette itself, accessibility-contrast research, and brand-system authorship are excluded.
#9Typography integrationDetails
Integration of web fonts (loading strategy, scale, fallbacks) using fonts licensed by the client. Font selection, custom-typeface design, and license procurement are excluded.
#10Icon library integrationDetails
Integration of an existing icon library (Lucide, Heroicons) or of client-supplied SVG icons. Custom-icon illustration and icon-system design are excluded.
#11UI animation implementationDetails
Implementation of UI animations (Framer Motion / CSS transitions) against the agreed motion brief. Motion-design direction, storyboarding, and bespoke micro-interaction authorship are excluded.
#44Logo design creationAnchor
Logo design creation is excluded. SessDev can technically integrate approved logo assets, but concept ideation, visual exploration, and design iterations are outside engineering scope unless explicitly quoted.
#45Brand-guidelines authorshipAnchor
Brand strategy and guideline authorship are excluded from this service layer. SessDev implements existing brand systems technically (tokens, fonts, usage constraints) but does not author the brand framework unless separately scoped.
Tracking & marketing
#12Analytics provider integrationDetails
Integration of an analytics provider (GA4, Plausible, PostHog, etc.) behind a consent gate. The provider account, billing, dashboarding, and reporting are owned by the client.
#13Marketing pixel integrationDetails
Integration of marketing pixels (Meta, TikTok, LinkedIn, Google Ads) behind a consent gate. Campaign creation, audience configuration, and ad spend are owned by the client.
#14Tag-manager container setupDetails
Setup of a tag-manager container (Google Tag Manager or equivalent) — container wiring only. Tag/trigger/variable configuration and ongoing tag-manager operation are owned by the client or their marketing team.
#15Email-capture endpoint integrationDetails
Integration of an email-capture endpoint with the client's ESP (Mailchimp, Brevo, ConvertKit, etc.). The ESP account, list segmentation, automation flows, and email-marketing strategy are owned by the client.
#16Cookie / consent banner setupDetails
Setup of a cookie/consent banner (Cookiebot, Termly, or open-source equivalent) with category gating wired to analytics/pixels. The chosen provider account and ongoing policy review are owned by the client.
#46Paid ads campaign managementAnchor
Paid advertising operations are excluded (Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, and equivalents). Campaign strategy, media buying, optimization, and performance reporting are not part of engineering delivery.
#47Social-media managementAnchor
Social-media management is excluded. SessDev may wire technical integrations when required, but content calendars, publishing operations, community management, and growth programs remain client-owned.
Media pipelines
#17Image-transformation pipelineDetails
Setup of an image-transformation pipeline (next/image + Vercel/Supabase image CDN) with responsive variants and modern formats. Photo retouching, art direction, and image sourcing are excluded.
#18Media storage bucket setupDetails
Provisioning of a media storage bucket (Supabase Storage or S3) with signed-URL access policies and folder structure. Bulk asset upload, metadata tagging, and library curation are excluded.
#19Media-upload UIAnchor
Implementation of an authoring/admin UI for media uploads wired to the storage bucket. Day-to-day media management and asset moderation are owned by the client.
#20Gallery component setupAnchor
Setup of a gallery component (carousel, grid, or lightbox primitives) wired to the media source. Curation of which assets to display and editorial sequencing are owned by the client.
#21OpenGraph preview-image pipelineAnchor
Setup of an OpenGraph preview-image pipeline (static export or dynamic OG generation). The visual design of OG cards and per-page art direction are owned by the client.
#22PDF asset servingAnchor
Serving of downloadable PDF assets from files supplied by the client. PDF authoring, design, and per-version document control are owned by the client.
#48Photography productionAnchor
Photography production is excluded, including shooting, retouching, curation, and rights administration. SessDev integrates only final approved photo assets into engineered surfaces.
#49Video production and editingAnchor
Video production and editing are excluded from base delivery. SessDev can implement playback and delivery infrastructure, while scripting, filming, editing, and post-production remain external responsibilities.
Third-party licenses
#23Font license wiringAnchor
Wiring of licensed web fonts. The client is the licensee and payer of record vis-à-vis the foundry, Adobe Fonts, Google Fonts paid tiers, or any other foundry account.
#24Stock asset wiringAnchor
Wiring of licensed stock assets (photo, video, illustration, audio). The client holds the underlying license, and SessDev integrates the assets within their license terms.
#25Paid plugin / library integrationAnchor
Integration of paid plugins or commercial libraries. The client is the commercial-license holder; renewal, support contracts, and entitlement management are the client's responsibility.
#26Map provider integrationAnchor
Integration of a map provider (Mapbox, Google Maps, MapTiler, etc.). The client is the account holder, API-key owner, and payer of record for usage-based billing.
#27Payment provider integrationAnchor
Integration of a payment provider (Stripe, PayPal, Mercado Pago, etc.). The client is the merchant of record, KYC/AML compliance is the client's responsibility, and settlement flows to the client's bank account.
#28Third-party iframe / widget embedAnchor
Embedding of third-party iframes or widgets (Calendly, Typeform, Tally, Intercom, etc.). The client is the account holder of the embedded service and owns its configuration.
#50License procurement and feesAnchor
Procurement and payment of third-party licenses are excluded. SessDev may integrate licensed components, but the client remains payer of record for fonts, plugins, stock assets, and commercial SDKs.
#51Third-party subscription feesAnchor
Recurring fees for third-party services are excluded from engineering scope. Vendor subscriptions (SaaS tools, API quotas, add-ons) remain on the client's billing accounts unless explicitly included in a signed commercial addendum.
Hosting & substrate
#29Cloud infrastructure provisioningAnchor
Provisioning of the Vercel project (Edge regions, build pipeline, environment scoping) on a SessDev-owned account. Account ownership remains with SessDev for the duration of the Managed retainer; transfer to the client occurs only upon IP Buyout.
#30Database & storage siloAnchor
Provisioning of a tenant-isolated Supabase project (Postgres database + storage bucket + auth) on a SessDev-owned organization. Data ownership remains with the client at all times; substrate ownership transfers only upon IP Buyout.
#31Domain & TLS/SSL wiringAnchor
Wiring of DNS records (A/AAAA/CNAME), TLS/SSL certificate issuance, and apex/www routing. The domain registrar account is the client's, and registrar fees are the client's responsibility.
#32Transactional email wiring (dual-rail)Anchor
Dual-rail transactional email wiring: (a) SessDev's own Resend account for platform/operational notifications (intake, billing, admin), and (b) the client's own Resend/Postmark/SendGrid account for application emails sent on the client's behalf. The client owns the application-email account and sender domain.
#33SLA monitoring setupAnchor
Setup of uptime monitoring and incident-response status page (Better Stack or equivalent) under the Shield retainer. Available exclusively to the Managed track.
#52Domain registration and renewal feesAnchor
Domain registration and renewal fees are excluded. SessDev can assist with DNS/TLS configuration, but registrar ownership and recurring domain charges remain with the client.
#53Cloud-vendor usage feesAnchor
Cloud-vendor overages and external infrastructure fees are excluded unless covered by an active Shield/Care contractual envelope. Any over-envelope usage is quoted, approved, and billed separately.
Maintenance (Shield + Care)
#34Automated backups SLAAnchor
Shield: automated database and storage backups with a documented RPO/RTO. Managed-track only — clients on the 1-Shot / Self-Hosted track operate their own backup discipline.
#35Security-patch managementAnchor
Shield: dependency and runtime security-patch management with prioritized remediation. Managed-track only.
#36Uptime SLA & incident responseAnchor
Shield: defined uptime SLA with an explicit incident-response window. Managed-track only.
#37Quarterly dependency auditAnchor
Shield: quarterly dependency audit and CVE-remediation report. Managed-track only.
#38Infrastructure cost coverageAnchor
Shield: coverage of SessDev-owned substrate costs (Vercel, Supabase) for the duration of the retainer at the tiered usage envelope. Managed-track only. Overage outside the envelope is billed separately and disclosed in advance.
#39Care hours bankAnchor
Care: a monthly bank of hours for content updates, configuration tweaks, and small enhancements. Unused hours expire at month-end unless the contract specifies otherwise.
#40CMS operator supportAnchor
Care: support and authoring assistance for the client's CMS operators (onboarding, how-to, troubleshooting). Excludes acting as the client's content team.
#41Change-request intake channelAnchor
Care: a documented change-request intake channel with ticketing and triage. Work outside the agreed scope is quoted and approved per request.
#54Ad-hoc maintenance outside Care/ShieldAnchor
Uncontracted maintenance is excluded. Ongoing updates, support, and operational continuity are provided only under active Care/Shield subscriptions or separately approved change orders.