sevenest. mmxxiv
seven / services / current plansOpen for part-time work
§ 05 / Services — current plans

A few ways
to work together.

A short, honest menu. A student developer open to interesting collaborations of all kinds.

Plan 01 · Web

Website design & development.

Let's talk/ project

Marketing sites, brand sites, campaign pages, and product landing pages — designed and built in code.

  • Brand site, campaign page, product page
  • Responsive across all devices
  • Design done entirely in code — no Figma handoff
  • Basic SEO setup included
  • Source code and deployment at handover
Tell me about your project
Plan 02 · Full-stack · Most common

Full-stack product development.

Let's talk/ project

E-commerce, membership systems, back-office dashboards — anything that needs a real backend.

  • E-commerce site with payment & order integration
  • Membership system and user management
  • Admin dashboard and back-office tools
  • Stack: Next.js, PostgreSQL, TypeScript
  • Regular progress updates
  • Scope confirmed before starting
Tell me about your project
Plan 03 · Systems & App

Custom systems & app development.

Let's talk/ project

Custom internal tools, bespoke systems, and cross-platform mobile apps.

  • Custom systems and internal tooling
  • Cross-platform mobile app (iOS & Android)
  • Stack: Flutter, React Native, Swift, Java
  • API design and backend integration
  • App Store / Google Play submission
  • Pricing based on project complexity
Tell me about your project
§ 05.1 / Process
How an engagement unfolds.
A few simple steps. Posted here so you know what to expect before we start talking.
01
A clear brief.
Tell me about your project, what you need help with, and what a good outcome looks like. I'll write back within 48 hours.
02
A relaxed conversation.
A call or message exchange to confirm requirements, timeline, and how we'll work together.
03
Steady work.
Regular progress syncs, with clear goals confirmed at each milestone.
04
A clean handover.
Complete source code, documentation, and maintenance notes.
§ 05.2 / Not on the menu
Things I won't be helpful with.
A short, honest list — to spare us both the polite back-and-forth.
i.
Pure design work.

I have basic UI/UX sensibility and implementation skills, but I'm not a designer. For pure visual design, please find a professional designer.

ii.
Full-time commitments beyond student hours.

I'm a student — coursework comes first. I can't commit to full-time hours. All arrangements are made with my class schedule as the baseline.

iii.
Surveillance, gambling, weapons.

The boundary cases here are interesting; the principle isn't. I'd rather not, and I'd rather we don't argue about it.

iv.
"Need it by tomorrow" rush jobs.

Quality takes time. Rushed delivery usually means sacrificed quality, which isn't good for either of us.

v.
Equity-only compensation.

Interesting projects can be discussed, but equity as the sole payment isn't realistic at the student stage.

vi.
NDAs before the first conversation.

Happy to sign one when there's something to sign about. Until then, an honest email is a better instrument.

§ 05.3 / Plain questions
Asked often enough to be written down.
№ 01Are you a student or working full-time?+

A sophomore CS student, and simultaneously Co-Founder & CTO of Deebug Co., Ltd. Coursework takes priority on weekdays; I invest free time in personal projects and collaborations.

№ 02What types of development can you do?+

Frontend (React, Next.js, Vite), backend (Node.js, Supabase, PostgreSQL), mobile apps (Flutter, SwiftUI), and full-stack integration. I also have Linux server ops and DevOps experience.

№ 03How do you arrange your working time?+

My class schedule is the baseline. Fixed weekly hours are negotiated before collaboration starts. I aim for a stable working rhythm to avoid uncertainty.

№ 04What real product experience do you have?+

VALKI, which I co-led, has 140k+ active users. The TronClass API tool is published on GitHub and NPM. The OLLM platform is in active MVP development.

№ 05How do I get started?+

Use the contact form to tell me about your project and what you need. I typically reply within 48 hours.

№ 06Can we work together on just one small feature or bug fix?+

Yes. Small tasks and one-off requests are welcome, especially when the problem is clear and the scope is well-defined.

Open · Accepting collaboration proposals

If there's a good fit — write to me, and we'll start a conversation about it.

Send that email →