SERVICES / WHAT WE BUILD
We start by deciding what to build.
AI can now take a product from plan to deployment quickly. That makes the choice of what to build matter more. We first learn who will use it and what is in the way, then pick and combine the document and text, image, voice and data AI that fits, and build something that works in real use.
What we take on
This is not a menu to pick one item from. We combine whatever your needs and situation call for.
-
AI strategy & planning
Want to use AI but not sure where to start? We look together at the problem you want solved, the data you have, and what today’s technology can realistically do. Where AI fits, we test it with a small prototype first; where it does not, we say so.
What we can build
- A shortlist of tasks where AI could help, in priority order
- A check of how ready your data is
- A small prototype with agreed success criteria
-
Custom AI services
Off-the-shelf AI tools not quite fitting your work? We learn who needs to do what, with which material, then pick from document and text, image, voice and data AI and combine what is needed into one service. It goes into a product your customers use or an internal tool, with clear points where people check the results.
What we can build
- Search that answers from your internal documents and shows its sources
- Reading photos or scanned documents, sorting them and pulling out the fields you need
- Voice Q&A, or summaries of calls and meetings
-
AI agents & workflow automation
Is your team copying the same data between tools and passing work along by hand at every step? We trace where the data comes from and who checks what. We connect the email, spreadsheets and internal tools you already use so AI can handle multi-step work, with points where people check or approve and a record of where anything failed.
What we can build
- Reading incoming email and attachments, sorting them and routing them to the right person
- Drafting recurring reports and sending them for review
- Processing logs and failure alerts
-
Data analysis & forecasting
Plenty of data, but hard to decide with it? We start from the decision you need to make, then collect and clean the data and show the metrics and trends behind it. Where the data allows, we go on to demand forecasts or anomaly detection, and agree accuracy targets with you after seeing the data.
What we can build
- Cleaning up data scattered across spreadsheets and databases
- A dashboard built around your decisions
- Demand forecasts and anomaly alerts
-
Web & app product development
Have an idea but not sure where first-time users will get stuck? We define who uses it, in what order, and the one task they must complete. We build websites, apps, SaaS and admin screens, including the screens AI features run on, with the accounts, permissions and payments needed to run them.
What we can build
- An app or SaaS with accounts, permissions and payments
- A website, with an admin screen for inquiries and bookings
- Improving a prototype built with AI tools, or a live service
Many projects combine several of these areas. Each project moves through understanding the customer, setting direction, building and review, then checks and launch.
Typical timelines by project type
Figures from before scope is settled.
- Marketing or landing siteMultiple languages, inquiry form, basic SEO2–3 weeks
- Admin tool or internal dashboardAuth, permissions, CRUD screens, metrics screens4–8 weeks
- SaaS MVPAccounts and permissions, subscription billing, one or two core features, production environment8–14 weeks
- Adding an LLM featureCollection, scoring, and reporting on an existing service3–6 weeks
- Improving an existing servicePerformance, structural cleanup, deployment automationTwo-week sprints
These estimates depend on scope and review timing. We confirm a project-specific schedule once the requirements are clear.
A quote based on your scope
Cost depends on the features, integrations, and target date. We can work through the details that are not yet decided.
A useful starting point
- What is not working right now, and what you want to change. This matters more than a feature list.
- How many people will use it, and in what roles.
- Existing systems to integrate with, including names and whether they are documented.
- Your target launch date, and whether it is fixed.
- A budget range. A bracket is enough, not an exact figure.
With those five we usually send a written scope, timeline, and cost draft within two business days. There is no charge if you read the draft and decide not to go ahead.
Working together and handing over
We agree on the schedule and support scope before work starts.
- How often we talk
- A 30-minute video call once a week on a fixed day, and the issue tracker and email in between. Decisions from the call are summarised in writing.
- What you see along the way
- We update the test environment and share progress weekly so you can try the work and discuss the next steps.
- Code ownership
- We hand over the code written for your project. The contract covers the timing of repository and access transfer, and the terms of third-party software.
- What handover includes
- Repository, infrastructure accounts, list of environment variables, deployment steps, operations docs, and notes on the main decisions. We answer questions for two weeks afterwards.
- Hours
- Weekdays 10:00–19:00 Korea time (UTC+9). Anything outside that, and the scope of incident response, is agreed in the contract.
- Rework
- Anything built differently from what we agreed, we fix at no cost. Where the scope itself changes after agreement, we re-estimate the schedule and cost and put it in writing.
When we work well together
We focus on web-based products. If you need a different format, tell us when you get in touch.
- A team ready to discuss the problem it wants to solve
- An identified decision maker
- A team able to review screens and documents together
- A project with an agreed plan for ownership after launch
Timelines depend on scope. See the estimates by project type.
What clients outside Korea ask first
-
Time zone
We respond on weekdays, 10:00–19:00 Korea time (UTC+9). Meetings outside those hours are agreed separately.
-
Language
Requirements documents, code review, and email are handled in English. English-language calls on request.
-
Contracts and payment
We contract as a Korean sole proprietorship. International payment is arranged by bank transfer.
-
Code ownership
We hand over the code written for your project. The contract covers the timing of repository and access transfer, and the terms of third-party software.
Questions before starting a project
What development projects can I bring to HYEROK IT?
AI strategy and planning, custom AI services, AI agents and workflow automation, data analysis and forecasting, and web and app product development. Which document, image, voice or data AI to combine depends on your needs and situation. If you are not sure which fits, tell us who will use it and what is getting in the way. We decide what to build together.
How is a development project priced?
Estimates depend on the features, external integrations and target date. Share the problem, users, existing systems, timing and budget range so we can outline scope and cost.
How long does development take?
Before scope is confirmed, examples are 2–3 weeks for a landing site, 4–8 weeks for an admin tool, 8–14 weeks for a SaaS MVP and 3–6 weeks to add an LLM feature to an existing service. The actual schedule depends on features, integrations and review timing.
How do we agree on a collaboration process?
We agree on the collaboration process, meeting schedule and response coverage before work begins, based on the project. We review screens and documents together and support English requirements, code reviews and email.
Do I receive the code and operating documentation?
We hand over project code, repositories, infrastructure accounts, an environment variable list, deployment steps and operating documentation. Transfer timing, third-party software terms and support scope are confirmed in the contract.
Can I inquire before I have a specification or budget?
Early ideas are welcome. Tell us who will use it, what is getting in the way, and what you want to change. Company or team name and budget are optional; we can clarify the features and scope together.
What is getting in the way?
Tell us who will use it, what is not working, and what you want to change. You do not need to know which AI to use, or have a finished feature list or a fixed budget.
A reply within one business day