Agents, sites, brand, and ongoing ops - fixed or monthly.

A landing or portfolio that books the next step.

Landing pages and portfolio / practice sites: structure, copy skeleton, deploy, analytics, and CTAs. Built for founders, freelancers, and web2 businesses (clinics, firms, studios). Speed and CTA hierarchy first, instead of a theme dump.

Best for: Public pages that convert, instead of brochure PDFs

• Founders / personal brands
• Portfolios (design, engineering, creative)
• Dental / med / law / local service (info + booking only)
• Agencies and productized consultancies

You keep

• -1-3 page landing or portfolio structure
• -Copy outline you approve; build in your stack or Next.js
• -Primary CTA path (book / form / Calendly) tracked
• -Mobile layout, title/meta/OG, sitemap hook
• -Deploy to your domain (Vercel or your host)
• -Handoff: how to edit content + one training call

A logo mark + kit your site, social, and decks can share.

Logo and wordmark options, color and type tokens, social templates, and usage rules. One clear face, not a purple gradient pack. Pairs with Site Surfaces or stands alone for a rebrand.

Best for: New brands, rebrands, and practices that look like every other template

• Startups and OSS projects
• Personal / founder brands
• Local professional practices

You keep

• -2-4 logo directions, then 1 locked mark (+ wordmark variants)
• -Color + type tokens (dark-first)
• -Social / OG template (SVG or PNG path)
• -One-page brand do / don't list
• -Optional: favicon + avatar crops
• -Source files you own (SVG/PNG)

Lower latency, clearer pipelines, RPC path you can run in prod.

RPC, gRPC streaming, transaction routing, and latency work for HFT, MEV, and bot teams. Scoped to the bottleneck you have.

Best for: Solana teams that need infra without a full hire

You keep

• -Bare-metal or cloud RPC topology that matches your risk
• -Yellowstone gRPC / shredstream path when needed
• -Transaction send path review (retries, tips, fanout)
• -Latency and reliability baseline + scorecard
• -Monitoring / alert stubs you can own
• -Written runbook for on-call handoff

A measured distribution loop you can run weekly.

The operator loop behind @nyk_builderz (~2.2K to 8.5K in ~4 months): content system, reply workflow, profile conversion, measurement. Hands-on with you. Separate from reachpeaks SaaS seats (waitlist product).

Best for: Founders who want inbound without ad spend

You keep

• -Profile + pin + CTA conversion pass
• -Content calendar + hook / format templates
• -Reply targeting workflow (ICP, not vanity)
• -Scorecard: impressions to profile to inbound
• -Experiment backlog (what to test next)
• -1 live working session to install the loop

Product path (not this package): reachpeaks waitlist · same operator DNA, separate product.

Someone ships and maintains your site, agents, and ops loop.

Monthly capacity: deploys, small features, agent skill updates, content slots, uptime hygiene. Built for founders and web2 practices that need a technical partner without a full-time hire. 24/7 emergency on-call only if scoped.

Best for: People and companies with a live surface that needs ongoing care

• Founders / solo operators
• Small companies (web2 + web3)
• Dental, med admin, law, real estate, agencies (ops + web; no licensed services)

You keep

• -Fixed monthly hours band agreed on the call
• -Priority queue (bugs, content, small features, agent tweaks)
• -Deploy + dependency hygiene on agreed stack
• -Monthly written summary of what shipped
• -Async chat window (Telegram or Slack)
• -Optional: one recurring live working session

Architecture and priorities that stay coherent under load.

Weekly strategy, architecture review, agent guidance, and distribution planning for teams that already ship. Judgment and decisions instead of a ticket mill. Pair with Maintainer when you also need hands on the keyboard.

Best for: Shipping teams that need judgment more than headcount

You keep

• -Weekly 60-min strategy / architecture call
• -Async review of plans, PRs, or agent configs
• -Agent and stack guidance (build vs buy)
• -Growth / distribution priorities when relevant
• -Slack or Telegram access between calls
• -Written decision notes after sessions